CODEWITHSUNDEEP
javascriptsafaricors
Marius
Marius

Reputation: 1759

Safari 10.1: XMLHttpRequest with query parameters cannot load due to access control checks

When trying a CORS request on Safari 10.1, on an URL which includes query parameters (e.g. https://example.com/api?v=1), Safari says

XMLHttpRequest cannot load due to access control checks

Chrome/Firefox works fine.

On requests from the page without the ?v=1, Safari works fine too.

I tried changing the server response header from

Access-Control-Allow-Origin: https://example.com

to

Access-Control-Allow-Origin: https://example.com/api?v=1

but that breaks Chrome.

Any suggestions?

Upvotes: 47

Views: 92869

Answers (6)

Madan Dale
Madan Dale

Reputation: 43

You should check the method type you calling may be - PUT, POST, GET etc.

Upvotes: -4

Henk Poley
Henk Poley

Reputation: 819

Your server needs to reply to the OPTIONS http method. Not only to GET/POST/PUT/DELETE. Safari silently requests this hidden in the background. You can discover this with a MITM-attack on the connection, e.g. Fiddler.

The OPTIONS request at least needs to respond with the Cross-Origin Resource Sharing (CORS) headers, e.g.:

  • Access-Control-Allow-Headers
  • Access-Control-Allow-Methods
  • Access-Control-Allow-Origin

Additionally: Your Web Application Firewall (WAF) or Application Security Manager (ASM) needs to allow the OPTIONS request to pass through to your server. Often this is blocked by default, because it gives some slivers of information about the attack surface variables (http methods & headers) used by your API.

Upvotes: 1

Andersson Mesa
Andersson Mesa

Reputation: 21

The problem is because it is necessary to be more specific in the data of the cors this does not happen in the other operating systems that do interpret it

This one worked for me for a back in php

header ("Access-Control-Allow-Headers: X-API-KEY, Origin, X-Requested-With, Content-Type, Accept, Access-Control-Request-Method");
header ("Access-Control-Allow-Methods: GET, POST, OPTIONS, PUT, DELETE");
header ("Allow: GET, POST, OPTIONS, PUT, DELETE");
$ method = $ _SERVER ['REQUEST_METHOD'];
if ($ method == "OPTIONS") {
     die ();
}

Upvotes: 1

Christian Kaal
Christian Kaal

Reputation: 232

If anyone comes across this error, it just occurred in the application I was building. In my case, it turned out to be a trailing / in the uri, which caused a 301 response, which was for some reason interpreted by Safari as a 500 response.

Upvotes: 3

mdeora
mdeora

Reputation: 4516

Trying following might work - 

Access-Control-Allow-Origin: <origin> | *

Upvotes: 2

Seika85
Seika85

Reputation: 2021

You're running into CORS issues.

Some possible causes:

  • The header Access-Control-Allow-Origin can only be set on server side, not in your clients script. (You did not make clear you did that correctly.)
  • Are you sure the protocol (http vs https vs maybe even file) is exactly the same?
  • If you may have multiple sub domains you need to setup your config (e.g. Apache) with something like "^http(s)?://(.+\.)?test\.com$ .
    The ^ marks the start of the line to prevent anything preceeding this url. You need a protocol and allowing both here. A subdomain is optional. And the $ marks the end of line (you don't need to set sub-pages, because origin is only host based).
  • As stated here adding Access-Control-Allow-Headers: Origin to the server configuration as well may be a solution. Try to compare the actual requests made my Safari to the successfull requests done by Firefox or Chrome to spot possible missing Headers as well (and maybe compare them to your server configuration as well).

Upvotes: 6

Related Questions