-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix XMLHttpRequest issues #3237
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this isn't mentioned explicitly in the linked bug reports, I have a couple questions:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops! That should have been included in the
fetch
bug report.:Status
is an intentionally invalid HTTP header which lets the macro writer explicitly set the response code. It is also used internally to get the status code from the request processing out to the wrapper layer. It could use an optional, or similar data type, but exposing those to the macro writers would be a bit of a trick. By specification, invalid HTTP headers must not be returned to the client, so it must be stripped out before the headers are returned. If the response is wrapped in a javascriptResponse
object (as thefetch
API does),Response
's constructor will throw an exception on invalid headers. Note this is different from undefined / extension headers (valid headers must not start with:
).The problem is the header filtering happens when the response body is received. If there is an exception thrown between when the header default values are set and the response body is received, the body-received function is not called, so the headers do not get filtered. When
fetch
then tries to handle the failed request, it chokes on the invalid header.So to sum up:
fetch
APIThat said, I think it might still have a problem outside the
fetch
API on internal server errors. Probably need to refactor it slightly to always explicitly filter the headers without calling the body-received function.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, nope, I can't see why the
MTXMLHttpRequest::recv
doesn't get called before the headers get retrieved. Especially given that the criticalonreadystatechange
call which triggers the javascript-side header processing happens after the headers should be handled.