[3.13] gh-112064: Fix incorrect handling of negative read sizes in HTTPResponse.read() (GH-128270)
          #129395
        
          
      
  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 parameter
amtofHTTPResponse.read(), which could be a negative integer,has not been handled before and led to waiting for the connection to close
for
keep-alive connections. Now, this has been fixed, and passing negative valuesto
HTTPResponse().read()works the same as passingNonevalue.(cherry picked from commit 4d0d24f)
Co-authored-by: Yury Manushkin [email protected]