➜

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 pitrou
Recipients catalin.iacob, neologix, pitrou, theamk, thomaslee
Date 2012-09-24.00:06:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348445185.77.0.739721617695.issue15991@psf.upfronthosting.co.za>
In-reply-to
Content 
I can reproduce under Debian testing, but not Debian stable nor Mageia 1.

I think this is really a bug in recent Debian/Ubuntu wget. By instrumenting SocketServer, I see that less requests are received than expected (e.g. ~350 instead of 400). It seems wget is trying to send further requests on the same client socket, even though the server responded with a HTTP/1.0 status line and without a "connection: keep-alive" header, indicating it doesn't want keep-alive. Even explicitly sending a "connection: close" header doesn't seem to change wget's behaviour.

If you pass "--no-keep-alive" to wget, though, it solves the issue.

Running Wireshark would probably help confirm this.
History
Date User Action Args
2012-09-24 00:06:25pitrousetrecipients: + pitrou, thomaslee, neologix, catalin.iacob, theamk
2012-09-24 00:06:25pitrousetmessageid: <1348445185.77.0.739721617695.issue15991@psf.upfronthosting.co.za>
2012-09-24 00:06:25pitroulinkissue15991 messages
2012-09-24 00:06:24pitroucreate