© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
I'd like to, but our development and deployment platform is Lucid 10.04 LTS. Even if it is fixed in v2.0, it does me no good until April of 2012 when we have our next scheduled upgrade. I don't have a spare cluster I install v2.0 and test the issue on.
This issue creates a problem for current boto release (and I assume other client libraries that demonstrate 408 timeout errors). Boto uses HTTP connection pooling and the extraneous text from the HEAD request stays in the connection buffer and breaks the next request that uses that connection. It took me almost two days to track this down. I hope if it is fixed in v2.0 that it can be backported and pushed to the LTS release. Right now I have a hacked boto that explicitly clears the buffer to work around this issue.
You can see the test script I submitted and follow the conversation as Mitchell Garnaat and I worked through the issue in this boto-dev thread:
http://
Thanks for your help on this!