aef1871 commented

I had to change the URLs to avoid spam filter

@dkocher commented

PUT /iPhone/2014/IMG_0041.JPG HTTP/1.1
Date: Sun, 16 Aug 2015 02:07:48 GMT
Expect: 100-continue
Content-Type: image/jpeg
Authorization: AWS IVECHANGEDTHIS:u1IVqOz0mrA4Hm0Qonf7LSBKfqU=
Content-Length: 2295546
Host: mys3backup.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.7.2.18004 (Windows 8/6.2) (x86)
HTTP/1.1 100 Continue
HTTP/1.1 400 Bad Request
x-amz-request-id: 3D597225908074BA
x-amz-id-2: wr8D5gUMVpja0b8ffgMWhoVYAs80kHL8g1zg0RgRXJsJqHvTBCGnXm/sHmMxUXGzE868FoJJdtI=
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Sun, 16 Aug 2015 02:07:32 GMT
Connection: close
Server: AmazonS3

<?xml version="1.0" encoding="UTF-8"?><Error><Code>RequestTimeout</Code><Message>Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.</Message><RequestId>3D597225908074BA</RequestId><HostId>wr8D5gUMVpja0b8ffgMWhoVYAs80kHL8g1zg0RgRXJsJqHvTBCGnXm/sHmMxUXGzE868FoJJdtI=</HostId></Error>

@dkocher commented

From https://forums.aws.amazon.com/message.jspa?messageID=116727

Since you are reusing connections, you should also take note of the guidance provided in the Amazon S3 best practices article regarding the maximum number of requests Amazon S3 will allow over a single connection (you should close the connection after 80-90 requests).

@dkocher commented

From https://aws.amazon.com/items/1904?externalID=1904

Amazon S3 will accept up to 100 requests before it closes a connection (resulting in 'connection reset'). Rather than having this happen, use a connection for 80-90 requests before closing and re-opening a new connection.

@dkocher commented

S3 responds with a Connection: Close response header after re-using the same connection 100 times. Therefore we handle this gracefully and this should not be an issue.

@dkocher commented

Possible fix in 18144 with fix HTTPCLIENT-1655 included.

Sends RST instead of proper FIN ACK sequence when using non-persistant connections

@dkocher commented

General performance fix in 18136 which could also affect this. Please update to the latest snapshot build available.