-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
XMLHttpRequest: response stream errors #27778
Conversation
https://crbug.com/602051 Service worker doesn't intercept sync XHR requests. cc: @domfarolino We can write a test with https://github.com/web-platform-tests/wpt/blob/master/fetch/api/resources/bad-chunk-encoding.py alternatively. |
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.
LGTM
@yutakahirano thanks for identifying that! I was wondering if there were non-ReadableStream ways to trigger this condition. That will make testing less cumbersome going forward and also reduces my worry about this being not handled well across callers (although most specification callers of fetch do not seem to account for it at the moment). |
And also clean up the way we manage XMLHttpRequest's response, which allows for simplifying "handle response end-of-body" and "handle errors". Tests: web-platform-tests/wpt#27778. Fixes #314.
And also clean up the way we manage XMLHttpRequest's response, which allows for simplifying "handle response end-of-body" and "handle errors". (Also ends up removing the remaining dependency on Streams.) Tests: web-platform-tests/wpt#27778. Fixes #314.
And also clean up the way we manage XMLHttpRequest's response, which allows for simplifying "handle response end-of-body" and "handle errors". (Also ends up removing the remaining dependency on Streams.) Tests: web-platform-tests/wpt#27778. Fixes #314.
For whatwg/xhr#314.
It seems Chrome does not throw exceptions here at all...