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] (ODATA-822) Async Batch Request: Bug in example 85


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

Ralf Handl updated ODATA-822:
-----------------------------

    Assignee: Martin Zurmuehl

> Async Batch Request: Bug in example 85
> --------------------------------------
>
>                 Key: ODATA-822
>                 URL: https://issues.oasis-open.org/browse/ODATA-822
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Martin Zurmuehl
>            Assignee: Martin Zurmuehl
>             Fix For: V4.0_ERRATA03
>
>
> We specified in 11.6 for asynchronous request in general :
>  "A GET request to the status monitor resource returns 200 OK once the asynchronous processing has completed. This response MUST include a Content-Type header with value application/http [...]. The response body MUST enclose a single HTTP response which is the response to the initial Data Service Request."
> In ODATA-240 we decided to use the exact same pattern also for async Batch Processing. But the example 85 doesn't reflect this fact, we missed to start the response with an 200 OK followed by the Content-Type application/http



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