Comment 7 for bug 885230

Thanks Mitch! You saved my day!

I am working with 2.0.3.

As I understand from the boto trace, it was boto that was bailing out, where as in S3, the server itself recognized the error and responded accordingly.

I would much prefer the latter behavior; that sounds more SaaSy. Not just because my library likes it that way, but for the sake of any one else who doesnt bother verifying the ETag returned by Walrus.