The OPTIONS method is now supported in HTTP web services, stored procedures, and functions. Among other things, this feature allows cross-origin resource sharing (CORS) to be supported by web services. See CREATE SERVICE statement [HTTP web service], CREATE PROCEDURE statement [Web service], and CREATE FUNCTION statement [Web service].
Obviously, if this is required for CORS and was added in v17, it won't help with v12.
Well, in my limited unstanding, the web server would only need to accept the OPTIONS method if your client tries to use CORS with other methods than GET or HEAD. If requests via GET and HEAD are sufficient, adding the according headers to the response should work with v12, too.
That's a good question, which is why I upvoted it back to zero :)
I too would like to see sample SQL that implements Cross-origin resource sharing (CORS).
"Using CORS enables a web programmer to use regular XMLHttpRequest . . ."
maybe he wants to know how to add correct headers to the server response... E.g. this http://dcx.sap.com/sa160/en/dbreference/http-header-function.html
Well, I don't have samples but v17 seems to have added something here:
Obviously, if this is required for CORS and was added in v17, it won't help with v12.
At present, there is no budget to purchase the SA 17 version!
Well, in my limited unstanding, the web server would only need to accept the OPTIONS method if your client tries to use CORS with other methods than GET or HEAD. If requests via GET and HEAD are sufficient, adding the according headers to the response should work with v12, too.
...go ahead, don't be shy, upvote the question :)
Not possible, I had already upvoted, counts are +2/-2=0:)