This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author v+python
Recipients demian.brecht, facundobatista, fdrake, martin.panter, orsenthil, quentel, remi.lapeyre, v+python
Date 2018-11-13.19:37:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1542137852.65.0.788709270274.issue10486@psf.upfronthosting.co.za>
In-reply-to
Content
That's interesting, Pierre, I hadn't really read the RFC carefully, to realize that many of the "missing" variables from Apache are HTTP headers, and that section 4.1.18 tell how to convert HTTP headers to meta variables.

The code in server.py 3.6 (Sorry, I should check the master branch) picks specific HTTP_ headers to include, rather than including them all per the rules. Doing the latter would go a long way toward being more compatible with Apache. I don't know if Rémi got his NGINX list from source code (looks like it) and if maybe NGINX also defines meta variables from the HTTP_ headers, that are not listed in the header file he seems to be quoting.

Unless the code has already been improved for Python 3.7, I think there is still some work to do to make server.py conform even to the RFC, if not be compatible with Apache.
History
Date User Action Args
2018-11-13 19:37:32v+pythonsetrecipients: + v+python, fdrake, facundobatista, orsenthil, quentel, martin.panter, demian.brecht, remi.lapeyre
2018-11-13 19:37:32v+pythonsetmessageid: <1542137852.65.0.788709270274.issue10486@psf.upfronthosting.co.za>
2018-11-13 19:37:32v+pythonlinkissue10486 messages
2018-11-13 19:37:32v+pythoncreate