Message295218
Why do you want to this? Encoding files on the fly seems out of scope of the SimpleHTTPRequestHandler class to me, but perhaps a more flexible API that could be plugged in by the user could be beneficial.
See xmlrpc.server.SimpleXMLRPCRequestHandler.accept_encodings and related code for an existing implementation.
Did you consider using Transfer-Encoding instead of Content-Encoding?
What do you propose to do with Content-Length? What would happen to code that uses persistent HTTP connections?
There are a few bugs open about this in the client: Issue 1508475 discusses handling compression (especially via Content-Encoding), and Issue 4733 talks about text decoding, which would depend on decoding the Content-Encoding first. |
|
Date |
User |
Action |
Args |
2017-06-05 23:22:01 | martin.panter | set | recipients:
+ martin.panter, quentel |
2017-06-05 23:22:01 | martin.panter | set | messageid: <1496704921.93.0.412422771016.issue30576@psf.upfronthosting.co.za> |
2017-06-05 23:22:01 | martin.panter | link | issue30576 messages |
2017-06-05 23:22:01 | martin.panter | create | |
|