Symptom
The behaviour is caused by incorrect Content-ID in the request body.
POST Practices HTTP/1.1
Content-ID: 110
POST Practices HTTP/1.1
Content-ID: 121
POST Practices HTTP/1.11
Content-ID: 132
After the Content-ID is increased to 10.
The Content-ID '11' is appended by one more digital 0
The Content-ID '12' is appended by one more digital 1.
….
The request with the wrong Content-ID cannot be processed by the backend.
500 error information has been returned.
Read more...
Environment
Landscape:
1. Mobile application is running on a Windows device and coded by C shape.
2. Using the IBM ODATA server as backend
3. SMP 3.0 is the middleware in between Client and Backend.
The issue Content-ID is concatenated and only occurred after the following upgrade:
- Client SDK:- SMP SDK SP13 PL02
- Server SDK:- SMP Server SP11 PL02
-
Windows Universal App running on Windows 8.1 (C#)
NOTE: The issue cannot be reproduced with iOS.
Product
Keywords
Content-ID, Create, $Batch, Request, Online Store, incorrect , KBA , MOB-SDK , SAP Mobile SDK , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview