Hello everyone: I have a web.py application that exposes two dozens URLs. On my development machine, I've tested the application both under the web.py development server as well as under mod_python over Apache. I've found the application to work for both situations.
I have the application deployed now on a production server under a similar setup, over mod_python inside a VirtualHost on Apache. However, any URL I try to get to gives out a 404 'not found' message. Seeing no errors in the logs, I wanted to make sure whether the application was getting hit at all or not, so I defined a `notfound()` function in the application to overwrite the default 404 message that is returned. To my surprise, when I accessed the URLs on the production box for the web.py application, I got the 404 and the new, custom message I had had put in place. Now, for the life of me, I can't figure out why the application is unable to find any of the URLs. I got the application to run on a non-standard port under the web.py development server on the production box to test whether the application worked at all there (in that, it wasn't going haywire due to any missing dependencies or errors), and sure enough, it worked absolutely fine there. I could visit any and all URLs properly. But once behind mod_python and Apache on the production box, it fails to find any URLs and simply lets out a 404. I should emphasize that I have a very similar mod_python/Apache setup running perfectly well on my development machine. I am really stumped. If I could get any clues or suggestions as to what I may be doing wrong or what could be the problem, I would be indebted and would greatly appreciate the effort. Thank you. Ayaz -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en.
