Changelog for python39-waitress-doc-2.1.2-74.1.noarch.rpm :

* Wed Jul 26 2023 Bernhard Wiedemann - Drop sphinx doctrees for reproducible builds
* Sat Jun 10 2023 ecsos - Fix build error for waitress:doc
* Wed May 03 2023 Martin Liška - Use sphinx-build and do not depend on removed build_sphinx in Sphinx 7.0 (boo#1211051).
* Fri Apr 21 2023 Dirk Müller - add sle15_python_module_pythons (jsc#PED-68)
* Thu Aug 18 2022 Ben Greiner - Remove code coverage checking for packaging tests
* Tue May 31 2022 Arun Persaud - specfile:
* be more specific in %files section- update to version 2.1.2 (bsc#1200126, CVE-2022-31015):
* Bugfix + When expose_tracebacks is enabled waitress would fail to 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 data was received across multple socket reads. This calculation has been corrected, and no longer will Waitress send back a 413 Request Entity Too Large. See https://github.com/Pylons/waitress/pull/376
* Security Bugfix + in 2.1.0 a new feature was introduced that allowed the WSGI thread to start sending data to the socket. However this introduced a race condition whereby a socket may be closed in the sending thread while the main thread is about to call select() therey causing the entire application to be taken down. Waitress will no longer close the socket in the WSGI thread, instead waking up the main thread to cleanup. See https://github.com/Pylons/waitress/pull/377
* Thu Mar 17 2022 Dirk Müller - update to 2.1.1 (bsc#1197255, CVE-2022-24761):
* Waitress now validates that chunked encoding extensions are valid, and don’t contain invalid characters that are not allowed. They are still skipped/not processed, but if they contain invalid data we no longer continue in and return a 400 Bad Request. This stops potential HTTP 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 only valid hex digits when parsing chunked encoding, and values such as 0x01 and +01 are no longer supported. This stops potential HTTP 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 sent by a remote contains only digits in accordance with RFC7230 and will return a 400 Bad Request when the Content-Length header contains invalid data, such as +10 which would previously get parsed as 10 and accepted. This stops potential HTTP desync/HTTP request smuggling Thanks to Zhang Zeyu for reporting this issue. See https://github.com/Pylons/waitress/security/advisories/GHSA-4f7p-27jc-3c36
* Fri Aug 27 2021 Stefan Schubert - Use libalternatives instead of update-alternatives.
* Fri Aug 27 2021 pgajdosAATTsuse.com- version update to 2.0.0 - Friendly Reminder This release still contains a variety of deprecation notices about defaults that can be set for a variety of options. Please note that this is your last warning, and you should update your configuration if you do NOT want to use the new defaults. See the arguments documentation page for all supported options, and pay attention to the warnings: https://docs.pylonsproject.org/projects/waitress/en/stable/arguments.html - Fix a crash on startup when listening to multiple interfaces. See https://github.com/Pylons/waitress/pull/332 - Waitress no longer attempts to guess at what the ``server_name`` should be for a listen socket, instead it always use a new adjustment/argument named ``server_name``. Please see the documentation for ``server_name`` in https://docs.pylonsproject.org/projects/waitress/en/latest/arguments.html and see https://github.com/Pylons/waitress/pull/329 - Allow tasks to notice if the client disconnected. This inserts a callable ``waitress.client_disconnected`` into the environment that allows the task to check if the client disconnected while waiting for the response at strategic points in the execution and to cancel the operation. It requires setting the new adjustment ``channel_request_lookahead`` to a value larger than 0, which continues to read requests from a channel even if a request is already being processed on that channel, up to the given count, since a client disconnect is detected by reading from a readable socket and receiving an empty result. See https://github.com/Pylons/waitress/pull/310 - Drop Python 2.7 and 3.5 support - The server now issues warning output when it there are enough open connections (controlled by \"connection_limit\"), that it is no longer accepting new connections. This situation was previously difficult to diagnose. See https://github.com/Pylons/waitress/pull/322
* Thu Oct 01 2020 Hans-Peter Jansen - Update to version 1.4.4 (2020-06-01) + Fix an issue with keep-alive connections in which memory usage was higher than expected because output buffers were being reused across requests on a long-lived connection and each buffer would not be freed until it was full or the connection was closed. Buffers are now rotated per-request to stabilize their behavior. + See https://github.com/Pylons/waitress/pull/300 + Waitress threads have been updated to contain their thread number. This will allow loggers that use that information to print the thread that the log is coming from. + See https://github.com/Pylons/waitress/pull/302- Switch to pytest, disable one test, that requires network- Create _multibuild for doc package It requires installation of base package now
* Wed Jun 17 2020 Jacek Tomasiak - make sure UTF8 locale is used when runnning tests
* Sometimes functional tests executed in python3 failed if stdout was not set to UTF-8. The error message was: ValueError: underlying buffer has been detached
* Mon May 18 2020 Petr Gajdos - %python3_only -> %python_alternative
* Thu Feb 06 2020 Marketa Calabkova - update to 1.4.3
* Waitress did not properly validate that the HTTP headers it received were properly formed, thereby potentially allowing a front-end server to treat a request different from Waitress. This could lead to HTTP request smuggling/splitting.- drop patch local-intersphinx-inventories.patch
* it was commented out, anyway