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

Use HTTP POST instead of PUT for assetStatusUpdateUrl #8

Open
quicksketch opened this issue Jun 20, 2014 · 0 comments
Open

Use HTTP POST instead of PUT for assetStatusUpdateUrl #8

quicksketch opened this issue Jun 20, 2014 · 0 comments

Comments

@quicksketch
Copy link

We recently ran into an issue when using this library that our assetStatusUpdateUrl URLs were returning HTTP 501 (not supported) errors. This turned out to be because this library uses a "PUT" request when the upload is finiahed, and our callback URL was hosted through Akamai, which by default does not allow PUT requests.

Really this shouldn't be a PUT request in the first place, since this URL is called after the file has been finished uploading. It's not really "putting" anything on our server, it's just notifying the server that the upload is complete.

I'd like to propose that we just change this PUT request to POST, to prevent these sort of problems, and to use the proper request type for the situation.

For reference: http://stackoverflow.com/questions/107390/whats-the-difference-between-a-post-and-a-put-http-request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant