Handle zero-length chunks on read #89
Open
Conversation
This file contains hidden or 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
This wasn't properly tested previously, so it was resulting in a short read. Also, because zero-length chunks are useless, put in basic protection against receiving too many. This protection isn't perfect, because it doesn't count across calls to `poll()` and it presently requires that two zero-length chunks are seen in the same call. That's OK, because the goal is to ensure that an attacker can't overload a reader with pointless work. If the reader is not overloaded, it might tolerate a few zero-length chunks, which is probably OK.
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.
This wasn't properly tested previously, so it was resulting in a short read. Also, because zero-length chunks are useless, put in basic protection against receiving too many.
This protection isn't perfect, because it doesn't count across calls to
poll()and it presently requires that two zero-length chunks are seen in the same call. That's OK, because the goal is to ensure that an attacker can't overload a reader with pointless work. If the reader is not overloaded, it might tolerate a few zero-length chunks, which is probably OK.