Message98678
Looking at the code in httplib it seems that response.will_close is set under the following circumstances,
1. HTTP version is 0.9
2. HTTP response header connection is set to close
3. Non-chunked content with a length of zero
This suggests that the underlying socket closure is valid under the conditions and that a subsequent response.read() should not be returning any content.
If you think this is still an issue, I'd suggest that you create a small example client/server script that
Client:
1. Opens a HTTP connection
2. Continues to read data from it and dumps it to the console.
Server:
1. Setup a script that does not close incoming HTTP connection requests and continues to keep sending data back to the client. |
|
Date |
User |
Action |
Args |
2010-02-01 19:42:43 | sijinjoseph | set | recipients:
+ sijinjoseph, Robert.Buchholz |
2010-02-01 19:42:43 | sijinjoseph | set | messageid: <1265053363.14.0.67141304999.issue7806@psf.upfronthosting.co.za> |
2010-02-01 19:42:41 | sijinjoseph | link | issue7806 messages |
2010-02-01 19:42:41 | sijinjoseph | create | |
|