Fix closing connection after read (#7867)

[matan1008]

What do these changes do?

This change keeps the connection open after reading the response to allow reuse of the connection

Are there changes in behavior for the user?

no

Related issue number

#7867

Checklist

Just wanted to make sure this change is welcomed before going over the checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> for example (588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the pr
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

[Dreamsorcerer]

This change keeps the connection open after reading the response to allow reuse of the connection

I'm pretty sure this does the opposite. You've removed the line of code which releases the connection so it can be reused.

I'm hoping your issue will be correctly resolved by #7869.

[Dreamsorcerer]

Superseded by #7879