Next thing to try would be to replace the WSGI scripts with one which echos WSGI environ.
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Displaying_Request_Environment Then compare what environ is for requests against different virtual hosts to see if that gives a clue. Strip any really sensitive information, trying not to change the meaning, and post it. Graham On 7 February 2012 12:55, Chris Cuilla <[email protected]> wrote: > Graham - > > Thanks for the response. A couple of things: > > Virtual hosts works fine when they are not mod_wsgi ghosts. When they > just plain, vanilla it works just fine. Not sure that matters, but > seems like the problems is some how related to mod_wsgi config. > >> First thing to check is that you have: >> >> NameVirtualHost *:80 >> >> directive present and that it isn't commented out. > > Yeah, that's set. > > >> One other thing you can do is add in a default VirtualHost as very >> first one, which from memory is defined as: >> >> <VirtualHost __default__:80> >> Deny from all >> </VirtualHost> >> >> With that in place, if named virtual host lookup is failing, will go >> to that and you will get a forbidden error, rather than it going to >> wrong virtual host. > > I tried that but it seems to shut out everything. > > Thanks for the suggestions. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" 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/modwsgi?hl=en. > -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
