Skip to content

Fetch: expand Response.redirect() assertions#10442

Merged
annevk merged 1 commit intomasterfrom
annevk/Response-dot-redirect
Apr 24, 2018
Merged

Fetch: expand Response.redirect() assertions#10442
annevk merged 1 commit intomasterfrom
annevk/Response-dot-redirect

Conversation

@annevk
Copy link
Copy Markdown
Member

@annevk annevk commented Apr 12, 2018

Needed for whatwg/fetch#664 and whatwg/fetch#600.

Safari already passes these. Chrome and Firefox have statusText returning OK.

Copy link
Copy Markdown
Contributor

@jakearchibald jakearchibald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@annevk
Copy link
Copy Markdown
Member Author

annevk commented Apr 23, 2018

That is explicitly not changed here, see whatwg/fetch#698.

@annevk annevk requested a review from jakearchibald April 23, 2018 17:07
Copy link
Copy Markdown
Contributor

@jakearchibald jakearchibald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@annevk annevk merged commit 507af0c into master Apr 24, 2018
@annevk annevk deleted the annevk/Response-dot-redirect branch April 24, 2018 16:17
annevk added a commit to whatwg/fetch that referenced this pull request Apr 24, 2018
HTTP/2 does not have a status message (reason phrase) and giving all of HTTP/2's responses `OK` as status message would not be ideal. Therefore this change to the empty byte sequence. As a side effect, that's also a better default for Response.redirect().

Tests: web-platform-tests/wpt#7274 (issue due to lack of HTTP/2 support) and web-platform-tests/wpt#10442 (for Response.redirect()).

Fixes #599 and fixes #664.

Potential follow-up: #698.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants