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

Always attempt to set the Connection: close response header #429

Merged
merged 3 commits into from
Feb 4, 2024

Conversation

zanieb
Copy link
Contributor

@zanieb zanieb commented Dec 21, 2023

While working on #428, I pondered the idea that closing the connection should cause client-side complaints of broken connections. It looks like Task.close_on_finish is sometimes set to true alongside a Connection: close header and other times not. If headers have not been written yet, it makes sense to always include Connection: close when close_on_finish is set. This pull request adds a utility that sets both of these values together. This results in better connection handling for clients.

There are a couple caveats:

  • If Connection already has a directive in the response headers, we will not set it
  • If headers have already been sent to the client, there is of course nothing we can do

There is also not particularly simple way to ensure that people call this method correctly unless we want to introduce a property for this variable — but I'm not really into properties with side-effects.

I believe this change does not invalidate #428 but it does also resolve #427.

@digitalresistor digitalresistor merged commit f737755 into Pylons:main Feb 4, 2024
27 checks passed
netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this pull request Jun 13, 2024
3.0.0 (2024-02-04)
------------------

- Rename "master" git branch to "main"

- Fix a bug that would appear on macOS whereby if we accept() a socket that is
  already gone, setting socket options would fail and take down the server. See
  Pylons/waitress#399

- Fixed testing of vendored asyncore code to not rely on particular naming for
  errno's. See Pylons/waitress#397

- HTTP Request methods and versions are now validated to meet the HTTP
  standards thereby dropping invalid requests on the floor. See
  Pylons/waitress#423

- No longer close the connection when sending a HEAD request response. See
  Pylons/waitress#428

- Always attempt to send the Connection: close response header when we are
  going to close the connection to let the remote know in more instances.
  Pylons/waitress#429

- Python 3.7 is no longer supported. Add support for Python 3.11, 3.12 and
  PyPy 3.9, 3.10. See Pylons/waitress#412

- Document that trusted_proxy may be set to a wildcard value to trust all
  proxies. See Pylons/waitress#431
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.

Broken connections with many concurrent HEAD requests
2 participants