baserev update by copy to link target

• Files Changed
• Browse Source

Dirk: this iss needed following you update of python-Sphinx

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

Drop sphinx doctrees for reproducible builds

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Fix build error for waitress:doc

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- add sle15_python_module_pythons (jsc#PED-68)

• Files Changed
• Browse Source

- Use sphinx-build and do not depend on removed build_sphinx
  in Sphinx 7.0 (boo#1211051).

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to version 2.1.2 (bsc#1200126, CVE-2022-31015):

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Remove code coverage checking for packaging tests

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

update to latest version

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- 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

• Files Changed
• Browse Source

- Use libalternatives instead of update-alternatives.

• Files Changed
• Browse Source

- 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

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source