Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

unsafeReceiveResponse that does not consume body #115

Merged
merged 1 commit into from
Aug 24, 2018
Merged

unsafeReceiveResponse that does not consume body #115

merged 1 commit into from
Aug 24, 2018

Commits on Aug 23, 2018

  1. unsafeReceiveResponse that does not consume body 

    This works when you know there is no body, no matter what the headers
say (HEAD requests, aesiniath#114)

This also works when the handler consumes whatever part of the body you
actually want to use, and then you close the connection afterwards (no
reusing for pipelining!)  Sometimes this is a lot faster than using
pipelining if you can, for example, skip a many GB download (aesiniath#113)
    @singpolyma
    singpolyma committed Aug 23, 2018
    Configuration menu
    Copy the full SHA
    5d48210 View commit details
    Browse the repository at this point in the history