[Twisted-web] t.i.e.ConnectionDone: Connection was closed
cleanly error, using getPage
exarkun at divmod.com
Wed Aug 23 20:49:45 CDT 2006
On Wed, 23 Aug 2006 17:46:47 -0700, Dimi Shahbaz <dshahbaz at fcoe.k12.ca.us> wrote:
>Using t.web.client.getPage, I am continually seeing a
>"t.i.e.ConnectionDone: Connection was closed cleanly error" exception. The
>same URL loads fine in Firefox. I have examined the request headers that
>FF was sending, and even tried emulating exactly** all those headers in
>getPage(..., headers=...), but that was no help. My timeout is set very
>high as well, so it's not that.
>However, in ethereal, the response headers from the server, and in fact the
>content the server was sending back, was identical between the FF request
>and the getPage() request. The data looks as though it's being received,
>but I still get that exception, and getPage's success callback is never
>Any insights before I dive into HTTPClientFactory?
>** the only difference I saw between the two requests was that FF's was
>HTTP 1.1, while getPage's was 1.0.
1.1 vs 1.0 probably makes the difference. Connection closed is probably being used to signal the end of the response. If getPage is not recognizing this as successful completion, it may be a getPage bug. Can you attach both traffic captures to a ticket in the tracker? http://twistedmatrix.com/trac/newticket (you'll need an account first).
>Dimi Shahbaz, Software Engineer Specialist
>California PASS Program
>Twisted-web mailing list
>Twisted-web at twistedmatrix.com
More information about the Twisted-web