No longer necessary to treat 304 responses specially. #322
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The end event should also be emitted for 304 (Not modified) responses. Starting with commit 182dcd3, there is no need to special handle these response statuses. Ensures that end is emitted also for 304 responses.
|
@mmalecki any hope of getting this in? As it stands, a 304 response will not emit an end event, unlike all other responses. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The end event should also be emitted for 304 (Not modified) responses.
Starting with commit 182dcd3, there is no need to special handle these response statuses.
Ensures that end is emitted also for 304 responses.