on 10-21-2019 12:40 PM
Hello to all!
I get net::ERR_EMPTY_RESPONSE when I try to create new entry in oData (with sap.ui.model.odata.v2.ODataModel) from SAPUI5.
I have .xsodata service, that exposed on XS Classic and SAPUI5`s frontend. SAP HANA Trace looks like nothing is happening (there are no records about inserting a new record).
When I`m try to POST new entry to oData with Postman, this works well. GET-request works well with SAPUI5.
Unfortunately, v2.ODataModel`s error callback is not very informative:
Any help is appreciated! Thanks!
Best regards,
Pavel Mazharov.
Hello everybody!
The problem was solved. This was a problem in the corporate network settings. I really don't know the real reason for this behavior, but when we added the SCP address to the firewall exceptions, everything worked fine.
P.S.: the $ batch request from the Postman works well when the request from the browser fails.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
did you debug your call at server side? can you call your service from postman?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Jun!
Thanks for your reply. I looked in SAP HANA Trace and did not find anything about the request from SAPUI5 (but I have logs if I make a request to the xsodata service from the Postman).
As I said, Postman works well with POST requests, unfortunately, I do not know how to generate a $batch request from Postman.
Best regards,
Pavel Mazharov
hi Pavel,
Please check the following thread:
https://answers.sap.com/questions/12888844/odata-batch-request-from-webide-fails.html
Thanks,
Vaibhav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vaibhav!
Thank you for you reply, but "prevent_xsrf" has been disabled in .xsaccess file. I tried to change this field to true, but I have another error:
403, message: "HTTP request failed", responseText: "Request execution failed due to missing or invalid XSRF token"
The most surprising is that there was no problem before, it appeared unexpectedly, the configuration was not changed anywhere.
Best regards,
Pavel Mazharov.
User | Count |
---|---|
87 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.