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

PRIORITY frames from server should be Connection Error #2507

Closed
martinduke opened this issue Mar 8, 2019 · 0 comments
Closed

PRIORITY frames from server should be Connection Error #2507

martinduke opened this issue Mar 8, 2019 · 0 comments
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus.

Comments

@martinduke
Copy link
Contributor

the very end of Section 4.2.3 of quic-http says:

PRIORITY frames received by a client MUST be treated as a stream
error of type HTTP_UNEXPECTED_FRAME.

Elsewhere, this kind of thing is a connection error. Making this a stream error seems problematic; if otherwise valid, if this goes out on the control stream a stream error may bring everything down anyway?

Here is the mailing list thread:
https://mailarchive.ietf.org/arch/msg/quic/ODlqMOxUP9W5RcZ5UIjTp2lKh4U

I believe the consensus is to make it a conn error; PR to follow.

MikeBishop pushed a commit that referenced this issue Mar 9, 2019
@MikeBishop MikeBishop added design An issue that affects the design of the protocol; resolution requires consensus. -http labels Mar 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus.
Projects
None yet
Development

No branches or pull requests

2 participants