[OLINGO-1554] Olingo V4 - Uniqueness of Content-ID in batch request - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Blocker
Resolution: Fixed
Affects Version/s: (Java) V4 4.8.0
Fix Version/s: (Java) V4 4.9.0
Component/s: odata4-client
Labels:
- V4
- batch
- clientCore
- odata4
- olingo
- olingo4
Environment:
SAP_GWFND 7.54 SP4

Description

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. [...]"

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

0001-OLINGO-1554-Fix-for-Uniqueness-of-Content-ID-in-requ.patch
16/Feb/22 10:45
9 kB
Prasanth Ganesh Rao

Activity

People

Assignee:: mibo

Reporter:: Kai Stritzelberger

Votes:: 1 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 11/Jan/22 11:28

Updated:: 26/Feb/22 07:26

Resolved:: 26/Feb/22 07:26