waitress Documentation Release 3.0.1 Pylons Project Developers June 08, 2024 CONTENTS 1 Extended Documentation 3 2 Change History 21 3 3.0.1 (unreleased) 23 4 3.0.0 (2024-02-04) 25 5 2.1.2 27 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 23 waitress Documentation, Release 3.0.1 24 Chapter

waitress Documentation Release 2.1.2 Pylons Project Developers May 30, 2022 Contents 1 Extended Documentation 3 2 Change History 21 3 2.1.2 23 4 2.1.1 25 5 2.1.0 27 6 2.0.0 (2021-03-07) 29 7 properly encode unicode thereby causing another error during error handling. See https://github.com/Pylons/waitress/pull/378 • Header length checking had a calculation that was done incorrectly when the corrected, and no longer will Waitress send back a 413 Request Entity Too Large. See https://github.com/Pylons/waitress/pull/376 3.2 Security Bugfix • in 2.1.0 a new feature was introduced that allowed the

waitress Documentation Release 2.1.1 Pylons Project Developers March 16, 2022 Contents 1 Extended Documentation 3 2 Change History 21 3 2.1.1 23 4 2.1.0 25 5 2.0.0 (2021-03-07) 27 6 1.4.4 (2020-06-01) 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 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

waitress Documentation Release 1.4.3 Pylons Project Developers February 03, 2020 Contents 1 Extended Documentation 3 2 Change History 19 3 1.4.3 (2020-02-02) 21 4 1.4.2 (2020-01-02) 23 5 1.4.1 and CPU usage going to a 100%. This was reported by Fil Zembowicz to the Pylons Project. Please see https://github.com/Pylons/waitress/ security/advisories/GHSA-73m2-3pwg-5fgc for more information. 21 the extra test cases. Please see the security advisory for more information: https://github.com/Pylons/waitress/security/advisories/ GHSA-m5ff-3wj3-8ph4 CVE-ID: CVE-2019-16789 4.2 Bugfixes • Updated

waitress Documentation Release 1.3.1 Pylons Project Developers August 27, 2019 Contents 1 Extended Documentation 3 2 Change History 19 3 1.3.1 (2019-08-27) 21 4 1.3.0 (2019-04-22) 23 5 1.2.1 (2019-01-25) environment that contains //testing/whatever as required. See https://github.com/Pylons/waitress/issues/260 and https://github. com/Pylons/waitress/pull/261 21 waitress Documentation, Release 1.3.1 22 Chapter now defaults to 1 and is deprecated pending removal in a future release. and https://github.com/Pylons/waitress/pull/246 4.2 Features • Add a new outbuf_high_watermark adjustment which is used to apply

unescape() u'Main \xbb About' Note The Jinja2 Markup class is compatible with at least Pylons and Genshi. It’s expected that more template engines and framework will pick up the __html__ concept silent=false to the settings and exceptions are propagated. 7.2 Pylons With Pylons 0.9.7 onwards it’s incredible easy to integrate Jinja into a Pylons powered application. The template engine is configured in config['pylons.app_globals'].jinja_env = Environment( loader=PackageLoader('yourapplication', 'templates') ) After that you can render Jinja templates by using the render_jinja function from the pylons.templating

(SQLAlchemy) is also available. Celery is easy to integrate with Django, Pylons and Flask, using the django-celery, celery-pylons and Flask-Celery add-on packages. • Overview • Example • Features • Documentation private correspondence. The Code of Conduct is heavily based on the Ubuntu Code of Conduct, and the Pylons Code of Conduct. 6.1.1 Be considerate. Your work will be used by other people, and you in turn ues • 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

some of which even have integration packages: Django django-celery Pyramid pyramid_celery Pylons celery-pylons Flask flask-celery web2py web2py-celery 1.1.2 Overview This is a high level overview of private correspondence. The Code of Conduct is heavily based on the Ubuntu Code of Conduct, and the Pylons Code of Conduct. 6.1.1 Be considerate. Your work will be used by other people, and you in turn • 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

Django ORM) is also available. Celery is easy to integrate with Django, Pylons and Flask, using the django-celery, celery-pylons and Flask-Celery add-on packages. • Overview • Example • Features • Documentation Documentation, Release 2.3.5 The Code of Conduct is heavily based on the Ubuntu Code of Conduct, and the Pylons Code of Conduct. 5.1.1 Be considerate. Your work will be used by other people, and you in turn ues • 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

Django ORM) is also available. Celery is easy to integrate with Django, Pylons and Flask, using the django-celery, celery-pylons and Flask-Celery add-on packages. • Overview • Example • Features • Documentation private correspondence. The Code of Conduct is heavily based on the Ubuntu Code of Conduct, and the Pylons Code of Conduct. 5.1.1 Be considerate. Your work will be used by other people, and you in turn ues • 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