Etienne Robillard <e...@gthcfoundation.org> added the comment:
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
<http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.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,
----------
Added file: http://bugs.python.org/file20288/unnamed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue4953>
_______________________________________
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 06/01/11 04:28 AM, Glenn Linderman wrote:
<blockquote
cite="mid:1294306110.0.0.541859342242.issue4...@psf.upfronthosting.co.za"
type="cite">
<pre wrap="">
Glenn Linderman <a class="moz-txt-link-rfc2396E"
href="mailto:v+pyt...@g.nevcal.com";><v+pyt...@g.nevcal.com></a> 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.
</pre>
</blockquote>
yes, lets not complexify anymore please... <br>
<blockquote
cite="mid:1294306110.0.0.541859342242.issue4...@psf.upfronthosting.co.za"
type="cite">
<pre wrap="">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.
----------
</pre>
</blockquote>
according to rfc2616...<br>
<br>
<span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Times New
Roman'; font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;
font-size: medium;">"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<span class="Apple-converted-space">Â </span><a
rel="xref"
href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.2";>7.2.2</a>),
or the desire to encrypt data over a shared transport.</span>"<br>
<br>
I may have not fully understood that part. Is "chunked" encoding what's
being used in MIME to allow<br>
large file uploads and properly handle multipart POST requests?<br>
<br>
Thanks,<br>
<pre class="moz-signature" cols="72">--
Etienne Robillard
Company: Green Tea Hackers Club
Occupation: Software Developer
E-mail: <a class="moz-txt-link-abbreviated"
href="mailto:e...@gthcfoundation.org";>e...@gthcfoundation.org</a>
Work phone: +1 514-962-7703
Website (Company): <a class="moz-txt-link-freetext"
href="https://www.gthc.org/";>https://www.gthc.org/</a>
Website (Blog): <a class="moz-txt-link-freetext"
href="https://www.gthc.org/blog/";>https://www.gthc.org/blog/</a>
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
</pre>
</body>
</html>
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
