OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (ODATA-527) Relative URLs in OData and the ability to put an OData service end-point behind an HTTP proxy

    [ http://tools.oasis-open.org/issues/browse/ODATA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34734#action_34734 ] 

Hubert Heijkers commented on ODATA-527:

Also, example 25, in part 2 - URL conventions, is incorrect as if $id's value in the first of the two examples was to be treated as relative to the request URL, we don't have another one to be relative with, then the id would become: http://host/service/Categories(1)/Products/Products(0) which obviously is incorrect. 

Having all these URLs be relative to the service root, which is effectively typically what is assumed (and a number of examples the resources are at the service root so its implicit in those cases) would fix this, currently we would not be able to have this URL be relative at all.

> Relative URLs in OData and the ability to put an OData service end-point behind an HTTP proxy
> ---------------------------------------------------------------------------------------------
>                 Key: ODATA-527
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-527
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format , OData CSDL, OData JSON Format, OData Protocol 
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD03
> It is often desirable to place an OData producer behind a (reverse) proxy. 
> This works best if all URLs in requests and responses are relative, so proxies don't have to touch the message bodies.
> Established mechanisms of interpreting URLs relative to the Content-Location header or the request URL don't work well with OData's URL conventions, which are constructed relative to the service root, so URLs starting relative to an entity would have to add ../ segments to go "down" to the service root and then "up" into the related entities. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]