on 03-10-2015 1:48 PM
Hi all,
we're developing an iOS App with a direct NW Gateway connection.
Actually all requests work fine but our problem is, that - in some cases - the OData request URL gets too long (because of a long system query option with $filter).
In the NW Gateway we traced the error in SMICM:
ERROR => Request URI too long, size=10220 [ictxxfilt.c 188]
ERROR => illegal request
We also tried to change the request method from GET to POST but in this case we get a service response with the following message:
"The Data Service Request contains SystemQueryOptions that are not allowed for this Request Type"
Is there any option to avoid this issue and send requests with longer URLs?
Thanks a lot four your help!
Regards,
Christian
Hi Christian,
Just a guess: you might try to send those problematic requests as Batch-Operations. That way the very long URLs would go into the HTTP Body. You always do that with a POST request. The URL is the one of the service document with $batch appended. In case of success the HTTP status code is 202 Accepted.
The request must contain a header which specifies a boundary marker:
Content-Type: multipart/mixed; boundary=batch_myboundary
The request body for a GET request looks like this:
--batch_myboundary
Content-Type: application/http
Content-Transfer-Encoding: binary
GET ProductSet('12345')/$YourURLOptions HTTP/1.1
--batch_myboundary
The line feeds and the hyphens "--" are obligatory.
POST requests are a bit more complicated. For details see http://help.sap.com/saphelp_gateway20sp10/helpdata/en/90/dc8363306c47d3b2fca1398f5de94b/content.htm?...
Best regards,
Ringo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.