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.

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

Client: allow configuring whether headers should be flushed immediately #104

Merged
merged 3 commits into from
Dec 17, 2021

Conversation

anmonteiro
Copy link
Owner

fixes #103

@anmonteiro anmonteiro force-pushed the anmonteiro/client-headers-flush branch from c995f90 to 3527511 Compare December 15, 2021 17:30
also:

- add a test that demonstrates the new behavior (and fails when the
  option is `true`)
- default `flush_headers_immediately` to `true` to preserve the current
  behavior. We might want to change that later, though that will require
  more test coverage (and possibly adding this argument to all current
  tests)
@anmonteiro
Copy link
Owner Author

Confirmed the following with tcpdump -A in piaf:

  • ~flush_headers_immediately:true sends 2 packets with request line + body
  • ~flush_headers_immediately:false sends a single packet with request line + body

@anmonteiro anmonteiro merged commit 8a42b9d into fork Dec 17, 2021
@anmonteiro anmonteiro deleted the anmonteiro/client-headers-flush branch December 17, 2021 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Configure headers flush on the client side
1 participant