None of your static files will work because you have: NameVirtualHost 192.168.1.6:80 <VirtualHost 192.168.1.6:80> ServerName www.healthcare.in ServerAlias healthcare.in Redirect / https://www.healthcare.in/index.py WSGIDaemonProcess healthcare.in processes=6 threads=15 display-name=%{GROUP} WSGIProcessGroup healthcare.in WSGIScriptAlias / /home/dev/wsgi-scripts/index.py <Directory /home/dev/wsgi-scripts> Options MultiViews +FollowSymLinks Order allow,deny Allow from all </Directory> </VirtualHost>
The WSGIScriptAlias directive, because it says '/', will intercept in this configuration all requests sent to the server. That is, it overrides DocumentRoot. Although you don't even have DocumentRoot set for the virtual host, and what is inherited from global server configuration is totally unknown. As explained in: http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines#Hosting_Of_Static_Files To have static files override WSGIScriptAlias mapping all the requests to the WSGI application, you must use Alias and AliasMatch directives. That is, have your static media be served from a sub URL and have all references get it from there. If the static media has to be at root of server, then you can use AliasMatch on select extension types. The only other way of doing it is as explained towards end of: http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines#The_Apache_Alias_Directive That is, use AddHandler to specify by extension type what files should be handled by mod_wsgi and if the root URL of the site also needs to be handled by WSGI application, then you need to use a mod_rewrite trick and potential fixups in the WSGI application. FWIW, I am reasonably sure I have been through this configuration for static files before with you. Your configuration seems though to be unchanged since October of last year at least. Graham On 14 August 2011 17:45, nitin chandra <[email protected]> wrote: > With a supposition that I will not be using (for the time being) SSL / https. > > So, in normal configuration of HTTP the web pages should be served, > with link to other pages also working / opening other pages. And *.js > files. > > That is not happening. Like wsgi set up with apache WITHOUT SSL was > ever configured. > > Then WSGI + Apache should server web pages without a glitch.... and > links to other pages also working . Currently not happening. > > Reg > > Nitin > > On Sun, Aug 14, 2011 at 6:44 AM, Graham Dumpleton > <[email protected]> wrote: >> You have lost me now as to how what you are currently describing >> relates to your problem with https. >> >> The impression I got was that after you disabled https virtual host >> that some page links from http site were failing because they were >> still referencing the https address. >> >> Can you explain again what the current problem is? >> >> Graham > > -- > 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.
