[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1028) 4.3.4: clarify relative URLs when a type-cast segment is present
[ https://issues.oasis-open.org/browse/ODATA-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-1028: --------------------------------- Proposal: Clarify that relative URLs passed with query option $id are relative to the service root. (was: Relative URLs passed with query option $id are relative to the request, as explicitly stated for other uses of $id. Add example for a relative URL with and without type-cast segments, showing the need for ../ to dive down beyond the type-cast segment.) > 4.3.4: clarify relative URLs when a type-cast segment is present > ---------------------------------------------------------------- > > Key: ODATA-1028 > URL: https://issues.oasis-open.org/browse/ODATA-1028 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData URL Conventions > Affects Versions: V4.0_ERRATA03 > Environment: Proposed > Reporter: Ralf Handl > Assignee: Ralf Handl > Fix For: V4.01_CSD02 > > > 4.3.4 Resolving an Entity-Id states that > The entity-id may be expressed as an absolute IRI or relative to the service root URL. > Example 23: request the entity representation for an entity-id > http://host/service/$entity?$id=Products(0) > This was correct until we introduced type-cast segments after $entity with ODATA-528. > Now relative URLs should rather be relative to the request URL, as in all other places. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]