tag:help.rubygems.org,2010-01-19:/discussions/problems/155-non-existant-pages-return-http-200-response-or-http-400-responseRubyGems.org: Discussion 2011-04-07T20:59:27Ztag:help.rubygems.org,2010-01-19:Comment/16194652010-05-06T20:04:07Z2010-05-06T20:04:27ZNon-existant pages return HTTP 200 response or HTTP 400 response<div><p>Maybe you're actively fixing it, but now it seems like the fancy
HTML not-found page indeed returns a 404 response.</p>
<p>Thanks,</p>
<p>-Bob</p></div>Bob McWhirtertag:help.rubygems.org,2010-01-19:Comment/16194652010-05-06T20:44:24Z2010-05-06T20:44:58ZNon-existant pages return HTTP 200 response or HTTP 400 response<div><p>Reported this on Gemcutter issues;</p>
<p><a href=
"http://github.com/qrush/gemcutter/issues/issue/180">http://github.com/qrush/gemcutter/issues/issue/180</a></p></div>Luis Lavenatag:help.rubygems.org,2010-01-19:Comment/16194652010-05-12T04:02:56Z2010-05-12T04:02:56ZNon-existant pages return HTTP 200 response or HTTP 400 response<div><p>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.</p>
<p><a href=
"http://github.com/qrush/gemcutter/issues#issue/143">http://github.com/qrush/gemcutter/issues#issue/143</a></p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/16194652011-03-18T20:22:16Z2011-03-18T20:22:16ZNon-existant pages return HTTP 200 response or HTTP 400 response<div><p>Going through Gemcutter's bugs queue...this has been fixed for a
while now since we're on Rails 3. Closing it!</p></div>Nick Quaranto