Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

broken pipe #6801

Closed
cyberduck opened this issue Aug 8, 2012 · 2 comments
Closed

broken pipe #6801

cyberduck opened this issue Aug 8, 2012 · 2 comments
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

2dcc655 created the issue

While attempting to upload files to AWS S3 I can only upload a little more than 100MB out of 1GB when the upload stops and the alert "broken pipe" comes up.

In other tickets with this topic (broken pipe) it's stated that the disk space quota is reached, but how can the disk quota on S3 be reached where there is no limit.....and my disk use is not even very big yet since I'm not able to upload bigger files?

Please help.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #7621. Fix in e1f5ff8 with Expect: 100-continue header for PUT requests that resolves broken pipe failures for uploads to buckets where a 307 Temporary Redirect is returned.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

1 participant