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

Internal Server Error due to wrong Request Content-Type [JIRA: RCS-151] #1091

Open
pmarques opened this issue Mar 13, 2015 · 2 comments

Comments

Projects
None yet
4 participants
@pmarques
Copy link

commented Mar 13, 2015

Hi, I was trying to use node-aws-sdk to set bucket policies but the SDK sends the request with the wrong Content-Type, "application/octet-stream". I'm not sure if there is something wrong on my side or if AWS S3 also supports this since it is its SDK.

To find the problem I was digging in the SDK code because the server response is just a 500 Internal Server Error. It could be nice to return at least something like "Unaccepted Content-Type in request".

@Basho-JIRA Basho-JIRA changed the title Internal Server Error due to wrong Request Content-Type Internal Server Error due to wrong Request Content-Type [JIRA: RCS-151] Mar 13, 2015

@pmarques

This comment has been minimized.

Copy link
Author

commented Mar 13, 2015

@shino

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2015

@pmarques Thanks for reporting.

As you indicated, 500 error is a bug of riak cs.
Also, it will be better for riak cs to accept application/octet-stream and whatever other content-type header values because the content of bucket policy request body should be XML and there are no alternatives to negotiate.

@shino shino added the Bug label Jan 19, 2016

@kuenishi kuenishi added this to the 2.1.2 milestone Feb 10, 2016

@kuenishi kuenishi modified the milestones: 2.2.0, 2.1.2 Mar 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.