You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Kai Stritzelberger (Jira)" <ji...@apache.org> on 2022/01/11 11:29:00 UTC

[jira] [Created] (OLINGO-1554) Olingo V4 - Uniqueness of Content-ID in batch request

Kai Stritzelberger created OLINGO-1554:
------------------------------------------

             Summary: Olingo V4 - Uniqueness of Content-ID in batch request
                 Key: OLINGO-1554
                 URL: https://issues.apache.org/jira/browse/OLINGO-1554
             Project: Olingo
          Issue Type: Bug
          Components: odata4-client
    Affects Versions: (Java) V4 4.8.0
         Environment: SAP_GWFND 7.54 SP4

            Reporter: Kai Stritzelberger


Currently, the Olingo client core uses an ascending index for the Content-ID header value which is unique in the individual changeset but not in the complete batch request when using BatchManager.addChangeset API.

This leads to problems with SAPs OData V4 services and is not correct according to the OData V4 spec:

11.7.7.1 Multipart Batch Request Body

"[...] Each body part representing an operation in the change set MUST specify a Content-ID header with a request identifier that is unique within the batch request. [...]"



--
This message was sent by Atlassian Jira
(v8.20.1#820001)