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 Guthur
Recipients Guthur, crchemist
Date 2009-06-01.18:23:52
SpamBayes Score 0.003324218
Marked as misclassified No
Message-id <1243880635.0.0.414262815091.issue6161@psf.upfronthosting.co.za>
In-reply-to
Content
But it must be somewhere, you don't make a seperate request to the 
server for the body, you just make the single HTTP request and the 
server serves that request.

Also this is surely aimed at developers, we can make the decision 
whether or not it is too large, and simply to, by making a HEAD request 
and checking the content-length header, and if its not available then 
don't continue with the request if we chose to take that action.

The point is that with out a body its not a HTTP response.

Admittedly some sort of streaming to file facility might be needed for 
the large requests, and that may require a significant effort to add.

Even if this can not be changed I think it should be clearly stated in 
the documentation that the request body needs to be explicitly read; I 
was trying to access it after making my request but of course it wasn't 
available, but the headers were and all status pointed to the request 
being served, which was rather confusing.

Thanks for the reply
History
Date User Action Args
2009-06-01 18:23:55Guthursetrecipients: + Guthur, crchemist
2009-06-01 18:23:55Guthursetmessageid: <1243880635.0.0.414262815091.issue6161@psf.upfronthosting.co.za>
2009-06-01 18:23:53Guthurlinkissue6161 messages
2009-06-01 18:23:53Guthurcreate