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

editorial advice for h2<->h3 error propagation #3602

Merged
merged 2 commits into from
May 5, 2020

Conversation

LPardue
Copy link
Member

@LPardue LPardue commented Apr 28, 2020

Fixes #2817

@LPardue LPardue requested a review from MikeBishop April 28, 2020 13:49
@LPardue LPardue added -http editorial An issue that does not affect the design of the protocol; does not require consensus. labels Apr 28, 2020
Copy link
Contributor

@MikeBishop MikeBishop left a comment

Choose a reason for hiding this comment

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

I think I'd invert the polarity of this, based on what I recall of the list discussion. Error codes largely reflect connection-local issues and mostly shouldn't be propagated. I'm inclined to lead with indicating an upstream failure via the HTTP status codes, then note that there are times it might be useful to proxy a specific stream error, such as REFUSED_STREAM.

@MikeBishop MikeBishop merged commit c6a32d2 into quicwg:master May 5, 2020
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

Successfully merging this pull request may close these issues.

Guidance for propogation of errors between H2 and H3
3 participants