Delta Regeer

http://opensource.adnovum.ch/mod_qos/ implements this, so it's a simple config flag for Apache.

waitress doesn't have any signal handlers defined and there are no cleanup methods or anything along those lines either, instead it relies on normal interrupts happening to the loop that...

Related: https://github.com/Pylons/waitress/pull/48 https://github.com/Pylons/waitress/pull/56

See issue comment here: https://github.com/Pylons/waitress/pull/269#issuecomment-559322234 The code referenced above wouldn't help solve for shutdown being configurable in terms of the timeout, in fact, because we never call into `asyncore.loop` we...

@mcdonc @tseaver @pauleveritt What are the ramifications of changing the docs license? If there is no want to change this from Agendaless side, then I will close this ticket.

Until there are good libraries available for it in Python, it is unlikely that Waitress will support it. As it currently stands HTTP/3 is not yet standardized and is a...

No, waitress at this point in time doesn't make any of that sort of information available.

Waitress will currently log when there are more requests in the queue than there are threads to process said requests. It is logged under `waitress.queue`. Additional information and or prometheus...

I don't really know if it is necessary to document it. I would like to convert the whole test suite to using pytest fixtures. To me it has always been...

Your application (WSGI app) is running inside a bunch of threads, and is not the one that sees the KeyboardException that is caught in server.py. Your application won't ever receive...