[OASIS Issue Tracker] Created: (ODATA-541) Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request

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

Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request
----------------------------------------------------------------------------------------------------------

                 Key: ODATA-541
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-541
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData Batch Processing Format 
    Affects Versions: V4.1_WD01
            Reporter: Matthew Borges


A client may want to group multiple data modification operations of a particular entity in a batch request and use ETags.  Currently, the client can use the ETag in the first data modification request but for all subsequent requests in the batch, it would have to use If-Match: *.

We should allow the If-Match header to reference the ETag that resulted in a previous data modification request in a batch (similar to how we use the Content-ID to refer to the URI of an entity).

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