s3 connector needs to proxy requests
Bug #369453 reported by
samuel-archive
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| petabox |
Triaged
|
Undecided
|
samuel-archive | ||
Bug Description
in reality amazon almost never issues 307 redirects
many clients cannot handle them, and it adds the requirement that clients do 100-continue for efficient data transfer on put
the best solution is to have the s3 server headend proxy requests to the data nodes in cases where a 307 would normally
be issued.
Revision history for this message
| samuel-archive (samuel-archive) wrote | #1 |
| Changed in petabox: | |
| assignee: | nobody → samuel-archive (samuel-archive) |
| status: | New → Triaged |
To post a comment you must log in.
A temporary fix is in place which has PUT and DELETE happen on the head end
This will work as long as the service does not become super popular