-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
Requests should not be provided to user if stream has been reset #30
Comments
Should this actually be done at this level? You could imagine a request with useful info sent, but the client doesn't want the response at all, and so sends a cancel after the headers. In this case, the app never knows what data was sent. Even if the stream was reset for another reason, the app may still want to be able to log that. |
Maybe... it seems OK to punt this question until later. It is not a breaking change either way I would say. |
This issue is kinda at odds with #536. I feel like the user of the Should we close this? |
For example, the server receives a request, then an invalid sequence of window updates. The stream is then reset. In this case, the server app should never see the request.
The text was updated successfully, but these errors were encountered: