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.

Sign up for GitHub

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

Client bug: Send request, then send reset before original HEADERS are flushed #125

Open
carllerche opened this issue Sep 27, 2017 · 2 comments
Open

Client bug: Send request, then send reset before original HEADERS are flushed #125

carllerche opened this issue Sep 27, 2017 · 2 comments

Comments

@carllerche
Copy link
Collaborator

It looks like this will cause the original HEADERS frame to be dropped and a RST_STREAM frame sent for that ID, which would be a connection level error.
@olix0r
Copy link
Collaborator

olix0r commented Sep 27, 2017

per offline convo:

we believe that the reset should just disappear the stream immediately, without informing the receiver of anything.

@nox
Copy link
Contributor

nox commented May 6, 2021

Same remark as on #30: this issue feels at odds with #536.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@carllerche @nox @olix0r