Waitress Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on a Reverse Proxy Design Differences from zope.server waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Socket Activation Glossary Change History 3.0.1 (unreleased) debugging and helping track this down. No longer strip the header values before passing them to the WSGI environ. See https://github.com/Pylons/waitress/pull/434 and https://github.com/Pylons/waitress/issues/432

Waitress Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on a Reverse Proxy Design Differences from zope.server waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Socket Activation Glossary Change History 2.1.1 Security Bugfix GHSA-4f7p-27jc- 3c36 2.1.0 Python Version Support Python 3.6 is no longer supported by Waitress Python 3.10 is fully supported by Waitress Bugfix wsgi.file_wrapper now sets the seekable, seek, and

Waitress Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Socket Activation Glossary Change History 2.1.0 Python Version Support Python 3.6 is no longer supported by Waitress supported by Waitress Bugfix wsgi.file_wrapper now sets the seekable, seek, and tell attributes from the underlying file if the underlying file is seekable. This allows WSGI middleware to implement things

Issues 103 44 Support and Development 105 45 Why? 107 Python Module Index 109 Index 111 ii waitress Documentation, Release 2.1.2 Waitress is meant to be a production-quality pure-Python WSGI server with any IPv4 address on port 8080. You can omit the host and port arguments and just call serve with the WSGI app as a single argument: from waitress import serve serve(wsgiapp) If you want to serve your application change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 3 waitress Documentation, Release 2.1.2 [server:main]

Issues 101 43 Support and Development 103 44 Why? 105 Python Module Index 107 Index 109 ii waitress Documentation, Release 2.1.1 Waitress is meant to be a production-quality pure-Python WSGI server with any IPv4 address on port 8080. You can omit the host and port arguments and just call serve with the WSGI app as a single argument: from waitress import serve serve(wsgiapp) If you want to serve your application change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 3 waitress Documentation, Release 2.1.1 [server:main]

Issues 107 46 Support and Development 109 47 Why? 111 Python Module Index 113 Index 115 ii waitress Documentation, Release 3.0.1 Waitress is meant to be a production-quality pure-Python WSGI server with any IPv4 address on port 8080. You can omit the host and port arguments and just call serve with the WSGI app as a single argument: from waitress import serve serve(wsgiapp) If you want to serve your application change this. There's an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress's WSGI gateway from a configuration file, e.g.: [server:main] use = egg:waitress#main listen = 127.0.0.1:8080

Waitress Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on a Reverse Proxy Design Differences from zope.server waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Socket Activation Glossary Change History 1.4.0 (2019-12-20) supports chunked encoding it does not support gzip and it is unable to pass that to the underlying WSGI environment correctly. Waitress DOES NOT implement support for Transfer-Encoding: identity eventhough

Issues 91 39 Support and Development 93 40 Why? 95 Python Module Index 97 Index 99 ii waitress Documentation, Release 1.4.3 Waitress is meant to be a production-quality pure-Python WSGI server with any IPv4 address on port 8080. You can omit the host and port arguments and just call serve with the WSGI app as a single argument: from waitress import serve serve(wsgiapp) If you want to serve your application change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 3 waitress Documentation, Release 1.4.3 [server:main]

Issues 83 35 Support and Development 85 36 Why? 87 Python Module Index 89 Index 91 ii waitress Documentation, Release 1.3.1 Waitress is meant to be a production-quality pure-Python WSGI server with any IPv4 address on port 8080. You can omit the host and port arguments and just call serve with the WSGI app as a single argument: from waitress import serve serve(wsgiapp) If you want to serve your application change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: 3 waitress Documentation, Release 1.3.1 [server:main]

Waitress Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on IP addresses, on port 8080, you can omit the host and port arguments and just call serve with the WSGI app as a single argument: from waitress import serve serve(wsgiapp) Press Ctrl-C (or Ctrl-Break change this. There’s an entry point for PasteDeploy (egg:waitress#main) that lets you use Waitress’s WSGI gateway from a configuration file, e.g.: [server:main] use = egg:waitress#main listen = 127.0.0.1:8080