On 06/01/11 04:28 AM, Glenn Linderman wrote:
Glenn Linderman <v+python@g.nevcal.com> added the comment:
Etienne, I'm not sure what you are _really_ referring to by HTTP_TRANSFER_ENCODING. There is a TRANSFER_ENCODING defined by HTTP but it is completely orthogonal to character encoding issues. There is a CONTENT_ENCODING defined which is a character encoding, but that is either explicit in the MIME data, or assumed to be either ASCII or UTF-8, in certain form data contexts.
yes, lets not complexify anymore please...
Because the HTTP protocol is binary, only selected data, either explicitly or implicitly (by standard definition) should be decoded, using the appropriate encoding. FieldStorage should be able to (1) read a binary stream (2) do the appropriate decoding operations (3) return the data as bytes or str as appropriate.
Right now, I'm mostly interested in the fact that it doesn't do (1), so it is hard to know what it does for (2) or (3) because it gets an error first.
----------
according to rfc2616...
"Transfer-codings
are analogous to the Content-Transfer-Encoding values of MIME [7],
which were designed to enable safe transport of binary data over a
7-bit transport service. However, safe transport has a different focus
for an 8bit-clean transfer protocol. In HTTP, the only unsafe
characteristic of message-bodies is the difficulty in determining the
exact body length (section 7.2.2),
or the desire to encrypt data over a shared transport."
I may have not fully understood that part. Is "chunked" encoding what's
being used in MIME to allow
large file uploads and properly handle multipart POST requests?
Thanks,
--
Etienne Robillard
Company: Green Tea Hackers Club
Occupation: Software Developer
E-mail: erob@gthcfoundation.org
Work phone: +1 514-962-7703
Website (Company): https://www.gthc.org/
Website (Blog): https://www.gthc.org/blog/
PGP public key fingerprint: F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC
During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell