Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Support HTTP/2 #110

Closed
annevk opened this issue Jan 9, 2017 · 3 comments
Closed

Support HTTP/2 #110

annevk opened this issue Jan 9, 2017 · 3 comments

Comments

@annevk
Copy link
Member

annevk commented Jan 9, 2017 •
edited by wpt-issue-mover
Loading

It would be good to also have tests that go over HTTP/2. There are a couple of subtle differences with HTTP/1 and if HTTP/2 is on the rise it would be good to start covering it.

Differences I'm aware of:

  • Header casing can matter in HTTP/1
  • WebSocket only works in HTTP/1
  • Chunked encoding is only in HTTP/1 (this will matter when Fetch gets "upload streams")
@gsnedders
Copy link
Contributor

See also: #80. I think realistically that's only ever going to get resolved by supporting HTTP/2.

@annevk
Copy link
Member Author

annevk commented Jan 9, 2017

Well, we need to test #80 without HTTP/2 as well ideally. We'd cover a lot less potential failure paths otherwise.

@wpt-issue-mover wpt-issue-mover mentioned this issue Nov 20, 2017
Closed
@wpt-issue-mover
Copy link
Collaborator

This issue has been moved to web-platform-tests/wpt#8371; please continue all discussion there.

@w3c w3c locked and limited conversation to collaborators Nov 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gsnedders @annevk @wpt-issue-mover