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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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