I've seen a number of posts where someone says, "What happens if you just run dispatch.fcgi directly?" Every time I do it, I get a "500: internal server error" message. I was just curious if that's what's expected running it directly. I assume so, because my apps all work fine, but that's always bugged me. Pat
on 2006-01-30 14:05
on 2006-01-30 14:52
Dispather is used to call the rails handler which in turn will look into the routes.rb & decide the controllers, action with what parameter, so when u call the dispatch.fcgi directly, their are no parameters so it will give a routing error & hence in deployment mode you will get page not found, if ur not getting that error chk the server log.
on 2006-01-30 15:14
baggio:~/work/teore-1_0 pergesu$ ./public/dispatch.fcgi Status: 500 Internal Server Error [30/Jan/2006:07:10:54 :: 6800] starting [30/Jan/2006:07:10:55 :: 6800] terminated gracefully Nothing in any other logs.
on 2006-01-30 18:47
Since you're not speaking to the dispatcher in the FCGI protocol, I think the 500 is normal.
on 2006-01-30 18:59
On Jan 30, 2006, at 5:04 AM, Pat Maddox wrote: > http://lists.rubyonrails.org/mailman/listinfo/rails > Pat- 500 Internal Server error is the correct thing to see when you run dispatch.fcgi from the cli. It is expecting to be spoken to in the fcgi protocol and when its not it will return a 500. Once and for all running dispatch.fcgi from the cli will return a 500 error even when your server is set up perfectly. Cheers- -Ezra Zygmuntowicz Yakima Herald-Republic WebMaster http://yakimaherald.com 509-577-7732 firstname.lastname@example.org