Closed Bug 1346749 Opened 9 years ago Closed 6 years ago

CORS: allow redirect after successful CORS preflight

Categories

(Core :: DOM: Networking, defect, P2)

Product:
Core
Component:
DOM: Networking
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: annevk, Unassigned)

References

(Blocks 1 open bug)

Details

web-platform-tests: cors/redirect-preflight.htm Standard: https://github.com/whatwg/fetch/issues/204 (This was initially thought to be covered by bug 918767, but it was not.)
Note that Edge and WebKit already support this.
Actually, Chrome supports this too. So we should probably start implementing this to avoid hitting issues.
Priority: -- → P2
Any update on this bug? When are you planning to release it?
Just spent 3 hours getting nowhere running into this. The spec on this was updated two years ago so would like to see this land.
Blocks: fetch
Any updates on this bug? It is seriously hindering our development of a restfull API behind authentication. It works on Chrome, but fails on Firefox. Reproducable with the tests at https://w3c-test.org/cors/redirect-preflight.htm (also work on chrome, fail on firefox).
I just wanted to add an example of how this bug is breaking things. ActiveStorage in rails creates indirect links which redirect to the real file source when loaded but because of this bug ActiveStorage can not be used on Firefox with CORS.
The only remaining issue here is bug 1444278 I think (tested by fetch/api/cors/cors-redirect.any.html). The test mentioned in OP and comment 5 passes in Firefox Nightly.
Depends on: 1444278
Component: DOM → DOM: Core & HTML

These tests now all pass as far as I can tell.

Status: NEW → RESOLVED
Closed: 6 years ago
Component: DOM: Core & HTML → DOM: Networking
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.