Hello, I was playing with lighttpd and i found out that , that it basicaly defines a 404 error to redirect to /fcgihandler.fcgi
So, in my virtual host inside cherokee, i defined, this error handler, and bingo, web2py started to work perfectly with cherokee. Massimo , this is the page i used as a guide http://www.web2py.com/AlterEgo/default/show/184. This does not mention about the 404 error handler and redirection. Do you think, we should add this to the documentation ? Also, surprisingly, I did not have to run the fcgihandler.py from my terminal window along with my webserver for web2py to run. Each time, i run cherokee and open my web2py application, it just works. these are the processes i see, after i start cherokee. root 5835 1 0 13:05 ? 00:00:00 /usr/sbin/cherokee -d http 5837 5835 0 13:05 ? 00:00:00 /usr/sbin/cherokee- worker And the third process just starts up automatically when i run the web2py application from the web browser. http 5847 1 5 13:05 ? 00:00:00 /usr/bin/python /data/ inetpub/web2py/fcgihandler.py Where as , in lighttpd, if you do not run the above process manually, in a terminal window, lighttpd gives an internal server error 500. Is the automatic startup a desired behaviour for fast cgi ? please advice. cheers Arvind --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
