FF111 XMLHttpRequest/HTTP channel - strip Authorization on cross-origin redirect #19092
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
data:api 🐇
|
@queengooborg FYI |
queengooborg
requested changes
Mar 14, 2023
Co-authored-by: Queen Vinyl Da.i'gyu-Kazotetsu <vinyldarkscratch@gmail.com>
queengooborg
approved these changes
Mar 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FF111 strips the
Authorizationheader added by developers from cross-origin redirects in fetch(), XMLHttpRequest, and more generally theHTTP channel - see: https://bugzilla.mozilla.org/show_bug.cgi?id=1802086.The
fetch()changes were done in #19064 . This duplicates the exactly the same info for XMLHttpRequest andAuthorization. That makes sense because these build on fetch(), as per response in mdn/content#22533 (comment).
Other docs work for this can be tracked in mdn/content#22533