On Fri 27 Jan 2012 13:18, Catonano <caton...@gmail.com> writes: > So it seems to me that this workaround of indicating a http 1.0 request > introduces too much unpredictability from the servers; I'm probably > running in a not so common case so some shoddiness in servers > configurations is emerging
I know it's a year late, but I tracked this one down to the http-get code shutting down the write end of the socket for non-keep-alive connections. This appears to stop the bytes being written from readching their destination! Perhaps we would need to uncork the socket or something in the future; surely someone performance-oriented will come along later and fix it properly. Anyway, fetching friendfeed.com/ now works properly. Cheers, Andy -- http://wingolog.org/
