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 | ggenellina |
|---|---|
| Recipients | cosoleto, ggenellina |
| Date | 2007年09月26日.14:07:53 |
| SpamBayes Score | 0.0415476 |
| Marked as misclassified | No |
| Message-id | <1190815674.57.0.150807839533.issue1205@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This is a server bug. Internet Explorer 6 can't show the page either. The response is malformed; it uses chunked transfer, and RFC2616 section 3.6.1 says "The chunk-size field is a string of hex digits indicating the size of the chunk. The chunked encoding is ended by any chunk whose size is zero[...]" After the (first and only) chunk of around 63K, should come a 0-length chunk: a line with one or more digits "0" followed by CR+LF. But the server is not sending that last chunk, instead it sends lots of nul bytes, until eventually a CR,LF sequence arrives. Neither IE nor Python can handle that (IE keeps requesting the page again and again). wget is apparently a lot more relaxed and decides that the first chunk is good enough. Perhaps urllib/urllib2 could handle the error and raise a more meaningful exception in this case, but just ignoring the error doesn't appear to be the right thing IMHO. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月26日 14:07:54 | ggenellina | set | spambayes_score: 0.0415476 -> 0.0415476 recipients: + ggenellina, cosoleto |
| 2007年09月26日 14:07:54 | ggenellina | set | spambayes_score: 0.0415476 -> 0.0415476 messageid: <1190815674.57.0.150807839533.issue1205@psf.upfronthosting.co.za> |
| 2007年09月26日 14:07:54 | ggenellina | link | issue1205 messages |
| 2007年09月26日 14:07:53 | ggenellina | create | |