Skip to content
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

Jump to bottom

Support HTTP/2 #8371

Closed
wpt-issue-mover opened this issue Nov 20, 2017 · 4 comments
Closed

Support HTTP/2 #8371

wpt-issue-mover opened this issue Nov 20, 2017 · 4 comments
Labels
infra priority:backlog wptserve

Comments

@wpt-issue-mover
Copy link

Originally posted as w3c/wptserve#110 by @annevk on 09 Jan 2017, 10:25 UTC:

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")
@wpt-issue-mover
Copy link
Author

wpt-issue-mover commented Nov 20, 2017 •
edited by annevk

Originally posted as w3c/wptserve#110 (comment) by @gsnedders on 09 Jan 2017, 13:16 UTC:

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

@wpt-issue-mover
Copy link
Author

wpt-issue-mover commented Nov 20, 2017 •
edited by annevk

Originally posted as w3c/wptserve#110 (comment) by @annevk on 09 Jan 2017, 13:23 UTC:

Well, we need to test #7693 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
@annevk annevk mentioned this issue Nov 21, 2017
Closed
@annevk
Copy link
Member

annevk commented Mar 27, 2018

I learned from @jyasskin that HTTP/2 header values can contain 0x0A (and presumably 0x0C and 0x00 too). It'd be good to have tests to see what that does.

#7274 is another thing I'd like to test, though that's mostly about what happens to HTTP/1 features that HTTP/2 dropped in APIs that support both.

@annevk annevk mentioned this issue May 28, 2018
Closed
@foolip
Copy link
Member

foolip commented May 6, 2021

Now we do :)

@foolip foolip closed this as completed May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
infra priority:backlog wptserve
Projects
None yet
Milestone
No milestone
Development

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