fog/fog — Issue #612: Broken pipe on upload to eu s3 bucket
Author: nate
Created: 2011-11-16 05:05:38+00:00
State: open

I suspect that this issue is caused by:

http://docs.amazonwebservices.com/AmazonS3/latest/API/index.html?RESTObjectPUT.html

"To configure your application to send the request headers prior to sending the request body, use the 100-continue HTTP status code . For PUT operations, this helps you avoid sending the message body if the message is rejected based on the headers (e.g., authentication failure or redirect). For more information on 100-continue HTTP status code, go to Section 8.2.3 of http://www.ietf.org/rfc/rfc2616.txt."

More info:
http://davidjrice.co.uk/2010/10/26/amazon-s3-european-bucket-issues-paperclip-attachment_fu.html
https://github.com/jnicklas/carrierwave/issues/203
https://github.com/jnicklas/carrierwave/issues/161

We get it with one of our customers' buckets every single time we try to upload to it using fog, and this didn't happen with right-aws. We've even figured out how to locate which region their bucket is in on the fly and we're specifying it in the request. I've tried it sans https, I've tried manually specifying the host and region, I've tried just about everything one could try to get this to work (except modifying fog and excon to detect what I suspect is happening and behave accordingly).

Any help would be appreciated, or advice on how to fix this in excon and/or fog.