How does Firefox handle HTTP requests differently from other browsers?
We're using CORS to make a request to our backend API. We're using NGNIX/1.6.2 and what's happening is that I'm consistently getting 500 Internal Server errors, but on Safari and Google Chrome, I don't see it coming back with a 500 error. I'm assuming FF handles the HTTP request differently than Chrome and Safari. Does anyone have any knowledge of why would FF show the error vs. Chrome. It seems like Chrome, makes another request or has a different timeout vs FF just stops making the request.
I'm on Mac OSX, FF 38.0.1 the request are make on the same domain.
Just spiffballing here, so any help would be appreciated. Thanks in advance.
Jaime
Krejt Përgjigjet (2)
What is the error that you are receiving and what kind of encryption is being used? usually in the response there is some explanation why there was an error. https://tools.ietf.org/html/rfc2616#section-10.5.1
More on the recent changes for CORS in Firefox: MDN HTTP access control (CORS) "
Only uses GET, HEAD or POST. If POST is used to send data to the server, the Content-Type of the data sent to the server with the HTTP POST request is one of application/x-www-form-urlencoded, multipart/form-data, or text/plain. Does not set custom headers with the HTTP Request (such as X-Modified, etc.)
"
add_header 'Access-Control-Allow-Origin' is "Basic" does the server require authentication?
Most of the information is in that MDN article, I hope this helps clear it up.
If the CORS part were failing, I think you would get a 403 response and not a 500 response. Instead, I suspect some code in your script on the server is dying, perhaps because Firefox is not sending an expected header or the format is not as expected. I realize that's vague but we don't have much to go on here.
If you use an HTTP proxy to compare the requests from your different browsers, do you see any differences?
Are you using the OPTIONS technique from the above-linked article?