or Create a profile
06 May, 2010 05:59 PM
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
It would be fantastic if both of those cases returned exactly a
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.
3 Posted by Luis Lavena on 06 May, 2010 08:44 PM
Reported this on Gemcutter issues;
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.
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!
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.
3 people watching.
No more actions from RubyGems.org or the discussion starter are required.
This discussion is private.
Only you and RubyGems.org support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
Powered by Tender™.