condition that existed when creating a new HTTPChannel. See https://github.com/Pylons/waitress/pull/435 and https://github.com/Pylons/waitress/issues/418 With thanks to Dylan Jay and Dieter Maurer for their 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 3.0.0 (2024-02-04) Rename "master" git branch to "main" server. See https://github.com/Pylons/waitress/pull/399 Fixed testing of vendored asyncore code to not rely on particular naming for errno's. See https://github.com/Pylons/waitress/pull/397 HTTP Request

desync/HTTP request smuggling. Thanks to Zhang Zeyu for reporting this issue. See https://github.com/Pylons/waitress/security/advisories/GHSA-4f7p-27jc-3c36 Waitress now validates that the chunk length is desync/HTTP request smuggling. Thanks to Zhang Zeyu for reporting this issue. See https://github.com/Pylons/waitress/security/advisories/GHSA-4f7p-27jc-3c36 Waitress now validates that the Content-Length desync/HTTP request smuggling Thanks to Zhang Zeyu for reporting this issue. See https://github.com/Pylons/waitress/security/advisories/GHSA-4f7p-27jc- 3c36 2.1.0 Python Version Support Python 3.6 is no

implement things like range requests for example See https://github.com/Pylons/waitress/issues/359 and https://github.com/Pylons/waitress/pull/363 In Python 3 OSError is no longer subscriptable, this attempting to loop to find an socket that would work for use in the trigger. See https://github.com/Pylons/waitress/pull/361 Fixed an issue whereby BytesIO objects were not properly closed, and thereby would potential for random memory spikes/memory issues, see https://github.com/Pylons/waitress/pull/358 and https://github.com/Pylons/waitress/issues/357 . With thanks to Florian Schulze for testing/vaidating

potential header field-name confusion, it should have sent back a 400 Bad Request. See https://github.com/Pylons/waitress/issues/273 Security Fixes Waitress implemented a "MAY" part of the RFC7230 (https://tools environment that contains //testing/whatever as required. See https://github.com/Pylons/waitress/issues/260 and https://github.com/Pylons/waitress/pull/261 1.3.0 (2019-04-22) Deprecations The send_bytes adjustment adjustment now defaults to 1 and is deprecated pending removal in a future release. and https://github.com/Pylons/waitress/pull/246 Features Add a new outbuf_high_watermark adjustment which is used to apply backpressure

lowercase HTTP verbs. This change was made to fall in line with most HTTP servers. See https://github.com/Pylons/waitress/pull/170 When receiving non-ascii bytes in the request URL, waitress will no longer abruptly the connection, instead returning a 400 Bad Request. See https://github.com/Pylons/waitress/pull/162 and https://github.com/Pylons/waitress/issues/64 1.0.2 (2017-02-04) Features Python 3.6 is now officially asking for IP address instead of reverse DNS hostname. See https://github.com/Pylons/waitress/issues/149 and https://github.com/Pylons/waitress/pull/153 1.0.1 (2016-10-22) Bugfixes IPv6 support on Windows

org/], Pylons [http://pylonshq.com/] and Flask [http://flask.pocoo.org/], using the django-celery [http://pypi.python.org/pypi/django- celery], celery-pylons [http://pypi.python.org/pypi/celery-pylons] and is heavily based on the Ubuntu Code of Conduct [http://www.ubuntu.com/community/conduct], and the Pylons Code of Conduct [http://docs.pylonshq.com/community/conduct.html]. Be considerate. Your work will com/ask/django-celery/issues Flask-Celery: http://github.com/ask/flask-celery/issues Celery-Pylons: http://bitbucket.org/ianschenck/celery-pylons/issues Kombu: http://github.com/ask/kombu/issues Carrot: http://github.com/ask/carrot/issues

com/], Pylons [http://pylonshq.com/] and Flask [http://flask.pocoo.org/], using the django-celery [http://pypi.python.org/pypi/django- celery], celery-pylons [http://pypi.python.org/pypi/celery-pylons] and is heavily based on the Ubuntu Code of Conduct [http://www.ubuntu.com/community/conduct], and the Pylons Code of Conduct [http://docs.pylonshq.com/community/conduct.html]. Be considerate. Your work will com/ask/django-celery/issues Flask-Celery: http://github.com/ask/flask-celery/issues Celery-Pylons: http://bitbucket.org/ianschenck/celery-pylons/issues Kombu: http://github.com/ask/kombu/issues If you are unsure of the

com/], Pylons [http://pylonshq.com/] and Flask [http://flask.pocoo.org/], using the django-celery [http://pypi.python.org/pypi/django- celery], celery-pylons [http://pypi.python.org/pypi/celery-pylons] and is heavily based on the Ubuntu Code of Conduct [http://www.ubuntu.com/community/conduct], and the Pylons Code of Conduct [http://docs.pylonshq.com/community/conduct.html]. Be considerate. Your work will com/ask/django-celery/issues Flask-Celery: http://github.com/ask/flask-celery/issues Celery-Pylons: http://bitbucket.org/ianschenck/celery-pylons/issues Kombu: http://github.com/ask/kombu/issues If you are unsure of the

com/], Pylons [http://pylonshq.com/] and Flask [http://flask.pocoo.org/], using the django-celery [http://pypi.python.org/pypi/django- celery], celery-pylons [http://pypi.python.org/pypi/celery-pylons] and is heavily based on the Ubuntu Code of Conduct [http://www.ubuntu.com/community/conduct], and the Pylons Code of Conduct [http://docs.pylonshq.com/community/conduct.html]. Be considerate. Your work will com/ask/django-celery/issues Flask-Celery: http://github.com/ask/flask-celery/issues Celery-Pylons: http://bitbucket.org/ianschenck/celery-pylons/issues Kombu: http://github.com/ask/kombu/issues If you are unsure of the

some of which even have integration packages: Django django-celery Pyramid pyramid_celery Pylons celery-pylons Flask flask-celery web2py web2py-celery Overview This is a high level overview of the is heavily based on the Ubuntu Code of Conduct [http://www.ubuntu.com/community/conduct], and the Pylons Code of Conduct [http://docs.pylonshq.com/community/conduct.html]. Be considerate. Your work will ues/ Django-Celery: http://github.com/celery/django-celery/issues Celery-Pylons: http://bitbucket.org/ianschenck/celery-pylons/issues Kombu: http://github.com/celery/kombu/issues If you are unsure of