[OASIS Issue Tracker] Updated: (ODATA-41) Specify which URL formats are acceptable within $batch, and which to prefer

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-41:
----------------------------

    Component/s: OData Protocol v1.0
                     (was: OData Batch Processing Format v1.0)

> Specify which URL formats are acceptable within $batch, and which to prefer
> ---------------------------------------------------------------------------
>
>                 Key: ODATA-41
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-41
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>             Fix For: WD01
>
>
> Current OData server implementations allow some or all of the following URI formats within the multi-part batch requests:
> A) relative to the $batch URI, e.g. 
> GET People(1) HTTP/1.1
> B) absolute with separate Host header, e.g.
> GET /service/root/path/People(1) HTTP/1.1
> Host: myserver.mydomain.org
> C) absolute with schema, host, and port, and without Host header, e.g.
> GET https://myserver.mydomain.org/service/root/path/People(1) HTTP/1.1

-- 
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