Why don't I get 404s?

When I go to a missing page in my rails app, I get the 500.html page,
and this in my log output:

no route found to match “/asdasd” with {:method=>:get}
./script/…/config/…/vendor/rails/actionpack/lib/action_controller/
routing.rb:1057:in recognize_path' ./script/../config/../vendor/rails/actionpack/lib/action_controller/ routing.rb:1047:inrecognize’
./script/…/config/…/vendor/rails/railties/lib/dispatcher.rb:38:in
dispatch' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel/rails.rb: 85:inprocess’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel.rb:
549:in process_client' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel.rb: 548:inprocess_client’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel.rb:
617:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel.rb: 616:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel.rb:
605:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel.rb: 935:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel.rb:
934:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails: 119:inrun’
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel/
command.rb:211:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:227 ./script/../config/../vendor/rails/activesupport/lib/active_support/ dependencies.rb:140:inload’
./script/…/config/…/vendor/rails/railties/lib/commands/servers/
mongrel.rb:48
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in
require' ./script/../config/../vendor/rails/activesupport/lib/active_support/ dependencies.rb:147:inrequire’
./script/…/config/…/vendor/rails/railties/lib/commands/server.rb:39
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in
`require’
script/server:3

I get the same problem running on lighty. My 404.html page exists.
Any idea why it’s not showing up?

On 7/20/06, Jonathan del Strother [email protected] wrote:

When I go to a missing page in my rails app, I get the 500.html page,
and this in my log output:

no route found to match “/asdasd” with {:method=>:get}
./script/…/config/…/vendor/rails/actionpack/lib/action_controller/
routing.rb:1057:in `recognize_path’
./script/…/config/…/vendor/rails/actionpack/lib/action_controller/

Can you show your routes file?

On Thursday, July 20, 2006, at 2:55 PM, Jonathan del Strother wrote:

/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel/
mongrel.rb:605:in run' dependencies.rb:140:inload’

I get the same problem running on lighty. My 404.html page exists.
Any idea why it’s not showing up?


Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails

are you in development mode or production?

_Kevin
www.sciwerks.com

On Thursday, July 20, 2006, at 7:39 PM, Jonathan del Strother wrote:

./script/…/config/…/vendor/rails/actionpack/lib/action_controller/
mongrel.rb:617:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel/ dependencies.rb:147:inrequire’
are you in development mode or production?
map.logout ‘logout’, :controller => “accounts”, :action => ‘logout’

c8zANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
TlzBBrAMdtjQ524lHs3rbUTJHJjvrKhiok87kvhOf5OU9lPnj885Z1b6WnB6gfgWypECA
UNhcGUg
ZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwn
IzRUIPq
KoZIhvcNAQkFMQ8XDTA2MDcyMDE4MzkxNlowIwYJKoZIhvcNAQkEMRYEFMXodZfOPautr
zkwyJg7
Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails

Try running in production mode for a minute and see if the behavior goes
away.

_Kevin
www.sciwerks.com

On 20 Jul 2006, at 17:01, Kevin O. wrote:

./script/…/config/…/vendor/rails/railties/lib/dispatcher.rb:38:in
mongrel.rb:616:in run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails: /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:inrequire’
script/server:3

I get the same problem running on lighty. My 404.html page exists.
Any idea why it’s not showing up?

are you in development mode or production?

Development. Stack traces caused by other exceptions display fine.

Can you show your routes file?

ActionController::Routing::Routes.draw do |map|
map.resources :accounts
map.connect ‘’, :controller => ‘message’
map.login ‘login’, :controller => “accounts”, :action => ‘login’
map.logout ‘logout’, :controller => “accounts”, :action => ‘logout’
map.connect ‘:controller/service.wsdl’, :action => ‘wsdl’
map.connect ‘:controller/:action/:id’
end

I’m wondering if it’s due to a change in recent Edge Rails - does
anyone on Edge get normal 404s?

On 20 Jul 2006, at 20:34, Kevin O. wrote:

Try running in production mode for a minute and see if the behavior
goes
away.

Nope, same problem.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs