I believe there to be two solutions to this problem. Either you need to support the OPTIONS verb, or you could accept authorization via the request bode (ie in the POST fields) instead of as an auth header (as this will not trigger CORS to send an OPTIONS request)
EDIT: I was able to work around the OPTIONS request, however the response from the post does not include the "Access-Control-Allow-Origin" header, therefore the response is still rejected.
Please advise ASAP.
answered 29 Mar '16, 13:29
Oksana Serdyuk ♦♦
I have the need for CORS support also as I am invoking from a web page. Right now I am getting around it by proxying requests to my server first. This seems to work fine for the API (i.e. start job, get status) but the download of the results from https://ocrsdk.blob.core.windows.net still won't work.
answered 13 Dec '16, 02:43