RESOLVED CONFIGURATION CHANGED 104551
Custom XHR headers do not survive redirect with HTTP status 303 
https://bugs.webkit.org/show_bug.cgi?id=104551
Summary Custom XHR headers do not survive redirect with HTTP status 303
Dominik Röttsches (drott)
Reported 2012-12-10 06:42:22 PST
When sending custom content-type headers with XHR GET requests to a resource that responds with a 303 redirect the custom headers are not send to the new location - that's at least observable with the soup backend.
Attachments
Add attachment proposed patch, testcase, etc.
Dominik Röttsches (drott)
Comment 1 2012-12-10 09:06:40 PST
302, 307 and other status codes do not expose to the same problem.
Alexey Proskuryakov
Comment 2 2012-12-10 09:41:37 PST
From a description in RFC 2616, 303 does not redirect to a new location of the same resource - it's an entirely different resource, and it seems inappropriate to keep the header fields. What do other browsers actually do?
Anne van Kesteren
Comment 3 2023-05-12 23:42:57 PDT
We don't fail the relevant WPT tests so this ought to work today.
Note You need to log in before you can comment on or make changes to this bug.