Closed iamleek1337 closed 3 years ago
Waitress is actively developed.
It is common to use a web server proxy in front of waitress for web traffic logging. Consult your web server documentation for logging configuration.
Thanks for the reply :) I am not using any web server proxy. Accessing my website means directly accessing waitress. Is waitress incompatible with this scenario and requires a web server proxy?
It's generally not recommended simply because HTTPS support is only possible by running waitress behind a reverse proxy.
This library [1] is a port of the translogger that you can use as well and I'm sure there are many others.
With respect to the status of this issue, I think I'm going to close it. We'd be happy to accept PRs to improve the docs but otherwise there's nothing actionable here.
Thanks for the reply. :)
I understand that you're hesitant to add access logging to waitress itself. Makes sense to me: middleware can do this job. However, access logging is an essential feature and in the days of supply-chain-attacks, I'd want this feature to come from a reputable source. So, alternatively, since you're the maintainer of https://github.com/mmerickel/request-id anyway, please consider incorporating it into Pylons as a separate (small) project?
The docs https://docs.pylonsproject.org/projects/waitress/en/stable/logging.html currently use an archive.org link to
paste.translogger
, a project where I found the following quotes:Source: https://github.com/cdent/paste/blob/master/README.rst
Source: https://github.com/cdent/paste/issues/54
What is the modern, up-to-date alternative? Or is waitress in maintenance mode, too, and shouldn't be used for new projects?