On Sat, Sep 19, 2009 at 3:17 AM, Duncan Coutts wrote:

But that is exactly what makes me think it's a bug in the HTTP library. The HTTP library provides instances for String, strict ByteString and lazy ByteString. With one instance provided by the HTTP library your test program fails and with the other it works.

I see...

It not completely implausible that it could be the fault of the way we use the HTTP library. For example if we were holding onto the lazy ByteString for a long period without demanding all of it then perhaps that could upset the network flow by causing timeouts or something, however I don't think anything like that is going on here. The code pretty swiftly takes the response and writes the content out to disk.

As I mentioned in the Cabal ticket, I'd be very interested in hearing Sigbjorn's diagnosis before considering whether we want to work around the problem by switching to strict ByteString. If at all possible I would prefer to stick to lazy ByteString.

Okay, let's wait then. Thank you, Duncan. -- vvv