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

Error for not receiving SETTINGS frame as the first frame on a control stream #1697

Closed
ddragana opened this issue Aug 23, 2018 · 1 comment
Closed
Labels
-http editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@ddragana
Copy link
Contributor

The paragraph says the a SETTING frame must be the first frame on a control stream but it does not specifies which error should be sent if that is not the case.

A SETTINGS frame MUST be sent as the first frame of either control stream (see {{stream-mapping}}) by each peer, and MUST NOT be sent subsequently or on any other stream. If an endpoint receives an SETTINGS frame on a different stream, the endpoint MUST respond with a connection error of type HTTP_WRONG_STREAM. If an endpoint receives a second SETTINGS frame, the endpoint MUST respond with a connection error of type HTTP_MALFORMED_FRAME.

@MikeBishop
Copy link
Contributor

Also, the control streams are now not so prominent in the referenced section. I'm thinking a more generally clean-up is warranted, and perhaps even separating control vs. request/response streams.

@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -http labels Aug 27, 2018
@MikeBishop MikeBishop added the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Sep 27, 2018
@mnot mnot removed proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. labels Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-http editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

No branches or pull requests

4 participants