On Oct 15, 1:46 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > Hi, > > I'm baffled by a problem that leaves me out of any idea how to solve so far. > > I've got a TG2-based application that amongst other things makes use of > tw.jquery to fetch jquery JS-files. > > It works flawless when directly served by paster. > > Today I wanted to test the application deployment undermod_wsgi. > > So I created a bootstrapping-wsgi-script (my whole installation resides in a > virtualenv and is running from there standalone without a hitch) > > The page itself is rendered & loaded properly. > > However, various (and changing) parts of the subsequently fetched static > content, especially the JS-files, throws a 404. > > But the fun part is: if I use firebug to fetch the url in question into > another tab, *IT GETS DOWNLOADED*... most of the time, that is. If I > press "reload" very often, I get intermittent 404s also. > > I'm running apache2,mod_wsgi2.0, python2.5.
Why aren't you using latest mod_wsgi 2.3? > THis is the startup message: > > http://paste.turbogears.org/paste/9664 Are you still using mod_python? If not, disable it out of Apache as it can cause problems for mod_wsgi. Did you completely 'stop' and then 'start' Apache after making any recent changes, or at least touch the WSGI script file so daemon processes would be reloaded. > The vhost-conf: > > http://paste.turbogears.org/paste/9666 Why don't you have a ServerName directive inside VirtualHost? If only serving one site and using ServerName from main configuration context, you probably don't need the VirtualHost container then. > The boostrap-wsgi-script: > > http://paste.turbogears.org/paste/9667 > > If there is *anything* enlightening to say about this, I'm more than glad to > hear it. > > I had the high hopes that such kind of behavior that I've seen PHP exhibit > would be something from a better forgotten dark past... Can you make it clear whether the 404 is generated by Apache or by TurboGears? Post the lines from the Apache access log which show the 404 errors for the request. Are the URLs there what you expect to see? For more in depth debugging of request and response at WSGI level, use second recipe in: http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Tracking_Request_and_Response to capture the complete request and response. Look at them to see if they are what you expect. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
