Skip to content

Close all outstanding responses on client close #35

Closed

Description

@lovelydinosaur

Client close currently closes off any keep-alive connections.
Actually the behavior would be more neatly bounded if we forcibly close off all connections.

with SyncClient() as client:
    response = client.get(..., stream=True)
response.read()  # This should raise an error.

Activity

  1. added this to the v1.0 milestone on Sep 15, 2019
  2. jhtimmins commented on Oct 8, 2019

    @jhtimmins

    @florimondmanca is this still up for grabs? And if so, would it make a good first issue?

  3. florimondmanca commented on Oct 8, 2019

    @florimondmanca
    Contributor

    Hi @jhtimmins! There's already a PR for this over at #322, but unfortunately it seems to have slipped through.

    So feel free to take it up. I don't think the fix will be trivial, but you can take a crack at it and see where you end up. :)

  4. jhtimmins commented on Oct 9, 2019

    @jhtimmins

    Thanks @florimondmanca! Sounds great. I'll do that.

  5. lovelydinosaur commented on Dec 16, 2019

    @lovelydinosaur
    MemberAuthor

    Obsoleted by the more tightly bounded stream() API. (Which ensures that connections can only be held open within a stream() context block)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions