Saver doesn't follow HTTP Status Code 30x redirects

[kloudless]

Saver doesn't follow HTTP Status Code 30x redirects

[vinodc]

While we do follow redirects for GET requests (like downloads), uploads generally do not resend POST data on a redirect, since the redirect could be in response to a successful operation rather than a failure. We would not want to resend data on a success since it may not be expected, and even if it is, it may not be idempotent. I believe the HTTP spec does allow for the scenario you describe with a 307 response code, but I doubt the server you are talking about returns that.

[lutherism]

Hmm strange. This is a GET for downloads, and its failing in this case for me. Maybe because it was getting redirecting twice? The second time to a separate domain.

first response 301 for setting locale, second response 302 to S3.

Anyway, we are just using the direct URL now, so it may not be worth tracking down.

[vinodc]

Whoops, I misunderstood and replied too soon. This is the case where the Saver downloads the file and attempts to save it. I'll verify that we follow redirects on downloads for this particular case and get back with an update.

[lutherism]

Cool, no problem. Thanks Vinod.

On Thursday, April 2, 2015, Vinod Chandru [email protected] wrote:

Whoops, I misunderstood and replied too soon. This is the case where the
Saver downloads the file and attempts to save it. I'll verify that we
follow redirects on downloads for this particular case and get back with an
update.

—
Reply to this email directly or view it on GitHub
#18 (comment)
.

[vinodc]

I've been unable to reproduce this. The Saver URL is handled correctly through multiple redirects in my tests (both 301 and 302). If you could provide me with a test URL, I can help troubleshoot further.

[vinodc]

Please re-open this issue if you continue to encounter this problem.