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

404 or 406 returned depending on format #443

Closed
gonzoyumo opened this Issue Jul 19, 2012 · 1 comment

Comments

Projects
None yet
3 participants
@gonzoyumo

gonzoyumo commented Jul 19, 2012

Hi,
when trying go get info about a gem that is not found, different responses are returned depending on the format:

$ curl -I https://rubygems.org/api/v1/gems/wrong_name.xml
HTTP/1.1 406 Not Acceptable
$ curl -I https://rubygems.org/api/v1/gems/wrong_name.json
HTTP/1.1 404 Not Found
$curl -I https://rubygems.org/api/v1/gems/wrong_name.yaml
HTTP/1.1 406 Not Acceptable

I suggest to make this consistent and always return 404

@fnichol

This comment has been minimized.

Show comment
Hide comment
@fnichol

fnichol Nov 4, 2012

Contributor

Looking at this one, woot!

Contributor

fnichol commented Nov 4, 2012

Looking at this one, woot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment