transfer: close connection after excess data has been read - #5440
Closed
mkauf wants to merge 1 commit into
Closed
Conversation
For HTTP 1.x, it's a protocol error when the server sends more bytes than announced. If this happens, don't reuse the connection, because the start position of the next response is undefined.
bagder
approved these changes
May 21, 2020
bagder
left a comment
Member
There was a problem hiding this comment.
This seems entirely correct and I'm a little bit puzzled why we didn't do this already!
Did you look into adding a test case for this? I would be so good to make sure that we do right and have that verified with a test!
Contributor
Author
|
Thanks for the feedback! I will work on a testcase, but I need some time. |
Member
|
I had a go at a test case for this in #5458 |
Member
|
I could verify your fix with my test so I think it's fine to merge. The test it self has problems so we can't merge that until it get fixed - if I can figure out a fix. Otherwise I'll just have to discard it. |
Member
|
Thanks! |
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
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.
For HTTP 1.x, it's a protocol error when the server sends more bytes than announced. If this happens, don't reuse the connection, because the start position of the next response is undefined.
I'm not sure whether this is also the case for other protocols, so please review carefully.
Test:
response.sh:
Start the test server:
Send three requests with curl:
Output:
So the second response is processed, because after reading the excess bytes, the next response line happens to be "HTTP/1.1 200 OK". The third response is not processed, because the next response line is "Content-Length: 21" - even though the size of the second response is announced correctly by the server. Whether curl processes the response depends on the position of the "sleep" command in the response script.