Message135691
The errors seem to have gone away now, but there is still apparently a behaviour change - previously there was no error when a end_headers() call was omitted when handling a request, but now apparently an end_headers() call is needed to avoid the error.
Either omitting the end_headers() call was always an error but previously undetected, or the requirement to always call end_headers() is new and this should be documented. I'm not sure which of these is the case, but leaving open since I think the http.server documentation ought to be changed. Apart from this I think the issue can be closed. |
|
Date |
User |
Action |
Args |
2011-05-10 09:12:58 | vinay.sajip | set | recipients:
+ vinay.sajip, orsenthil, giampaolo.rodola, skrah, python-dev |
2011-05-10 09:12:58 | vinay.sajip | set | messageid: <1305018778.63.0.303156881029.issue12039@psf.upfronthosting.co.za> |
2011-05-10 09:12:57 | vinay.sajip | link | issue12039 messages |
2011-05-10 09:12:57 | vinay.sajip | create | |
|