[Cyberduck-trac] [Cyberduck] #8975: 400 Bad Request error for idle connection (was: S3 upload fails, starts from beginning)
Cyberduck
trac at trac.cyberduck.io
Fri Aug 21 13:13:37 UTC 2015
#8975: 400 Bad Request error for idle connection
------------------------+------------------------
Reporter: rb808 | Owner: dkocher
Type: defect | Status: new
Priority: normal | Milestone: 4.8
Component: s3 | Version: 4.7.2
Severity: normal | Resolution:
Keywords: | Architecture: Intel
Platform: Windows 10 |
------------------------+------------------------
Comment (by dkocher):
{{{
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>
}}}
--
Ticket URL: <https://trac.cyberduck.io/ticket/8975#comment:3>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list