Home → Problems →

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

Admin Functions

• Remove

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:

http://rubygems.org/gems/wrong.gem

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

http://rubygems.org/wrong.stuff

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

Thanks,

-Bob

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

   

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

   Thanks,

   -Bob

   Admin Functions

   • Split
   • Remove

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

   

   Reported this on Gemcutter issues;

   http://github.com/qrush/gemcutter/issues/issue/180

   Admin Functions

   • Remove

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

   

   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.

   http://github.com/qrush/gemcutter/issues#issue/143

   Admin Functions

   • Remove

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

   

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

   Admin Functions

   • Remove

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.