On 09/22/2010 02:46 PM, Marcel Hellkamp wrote:
An application should read all available data from
`environ['wsgi.input']` on POST or PUT requests, even if it does not
process that data. Otherwise, the client might fail to complete the
request and not display the response.
Oh, it's worse than
I just discovered a problem that affects most WSGI server
implementations and most current web-browsers (tested with wsgiref,
paste, firefox, chrome, wget and curl):
If the server closes the connection while the client is still uploading
data via POST or PUT, the browser displays an error message
Marcel Hellkamp wrote:
I just discovered a problem that affects most WSGI server
implementations and most current web-browsers (tested with wsgiref,
paste, firefox, chrome, wget and curl):
If the server closes the connection while the client is still uploading
data via POST or PUT, the
On Wed, Sep 22, 2010 at 2:46 PM, Marcel Hellkamp m...@gsites.de wrote:
I just discovered a problem that affects most WSGI server
implementations and most current web-browsers (tested with wsgiref,
paste, firefox, chrome, wget and curl):
If the server closes the connection while the client is
On Wed, Sep 22, 2010 at 5:34 PM, Robert Brewer fuman...@aminus.org wrote:
However, the caveat requires a caveat: servers must still be able to protect
themselves from malicious clients. In practice, that means allowing servers
to close the connection without reading the entire request body
At 08:34 AM 9/22/2010 -0700, Robert Brewer wrote:
Marcel Hellkamp wrote:
I would like to add a warning to the WSGI/web3 specification to address
this issue:
An application should read all available data from
`environ['wsgi.input']` on POST or PUT requests, even if it does not
process that
Benoit Chesneau wrote:
On Wed, Sep 22, 2010 at 5:34 PM, Robert Brewer fuman...@aminus.org
wrote:
However, the caveat requires a caveat: servers must still be able to
protect themselves from malicious clients. In practice, that means
allowing servers to close the connection without reading
