why http 307 internal redirect workig only on Chrome and not firefox?

Viewed 85

So I have an API endpoint to which CORS requests sent over http are redirected with the http 308 permanent redirect in the response. In Firefox, the response is as expected, a 308 status code with the upgraded https location header. In Chrome however, response with the header Non-Authoritative-Reason : HSTS is set, to which Chrome performs 307 an internal redirect. I understand why Chrome(cause of HSTS) does this, but how is this is behavior not implemented in Firefox. In Firefox, the browser just rejects the CORS response, while Chrome fakes a request and then upgrades automatically to the https version of the URL.

0 Answers
Related