Non-existant pages return HTTP 200 response or HTTP 400 response

Bob McWhirter's Avatar

Bob McWhirter

06 May, 2010 05:59 PM

Hi there--

In trying to make the Maven (java build tool) work with RubyGems, I've found that missing gems return a 400 response code (instead of a 404), such as:

Other none-existant pages return the fancy "no such page" HTML page, but with an HTTP 200 response code, misleading automated clients.

It would be fantastic if both of those cases returned exactly a 404 response.



  1. 1 Posted by Bob McWhirter on 06 May, 2010 08:04 PM

    Bob McWhirter's Avatar

    Maybe you're actively fixing it, but now it seems like the fancy HTML not-found page indeed returns a 404 response.



  2. Support Staff 2 Posted by Luis Lavena on 06 May, 2010 08:44 PM

    Luis Lavena's Avatar

    Reported this on Gemcutter issues;

  3. Support Staff 3 Posted by Nick Quaranto on 12 May, 2010 04:02 AM

    Nick Quaranto's Avatar

    We've had this problem for a while. I've heard Rails 3 handles cascading 404's better...but I'm still unsure of the best way to fix it everywhere.

  4. Support Staff 4 Posted by Nick Quaranto on 18 Mar, 2011 08:22 PM

    Nick Quaranto's Avatar

    Going through Gemcutter's bugs queue...this has been fixed for a while now since we're on Rails 3. Closing it!

  5. Nick Quaranto closed this discussion on 18 Mar, 2011 08:22 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac