➜

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 martin.panter
Recipients martin.panter, matrixise, orsenthil
Date 2015-11-07.01:49:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446860979.07.0.918184140085.issue21224@psf.upfronthosting.co.za>
In-reply-to
Content 
There is already Issue 23794 discussing HTTP 2. IMO it would be interesting to implement, but I’m not sure how appropriate it would be in Python’s standard library at this stage. But working on it could drive other improvements in the existing HTTP stuff, as Demian hinted.

What do you mean by supporting HTTP 1.1 in the future? The basic support is already there; you just have to manually enable it. Maybe there is scope for making 1.1 easier to use, perhaps with a BaseHTTP11RequestHandler (shorter: Http11Handler) class or something.
History
Date User Action Args
2015-11-07 01:49:39martin.pantersetrecipients: + martin.panter, orsenthil, matrixise
2015-11-07 01:49:39martin.pantersetmessageid: <1446860979.07.0.918184140085.issue21224@psf.upfronthosting.co.za>
2015-11-07 01:49:39martin.panterlinkissue21224 messages
2015-11-07 01:49:38martin.pantercreate