Thank you. We'll go ahead and make the change. Is there anything else that stands out in the configuration that suggests wsgi may be running as cgi?
-Imtiaz On Jan 26, 1:06 pm, Mark Sapiro <[email protected]> wrote: > On Jan 26, 8:43 am, contactimtiaz <[email protected]> wrote:> Here's > the apache config relevant to wsgi: > > > LoadModule wsgi_module modules/mod_wsgi.so > > > <Directory /docs/content/scripts> > > Addhandler cgi-script .py > > AddHandler wsgi-script .wsgi > > Options +ExecCGI > > </Directory> > > [...] > > > WSGIScriptAlias /scripts/targeted_content_test /docs/content/scripts/ > > targeted_content_test.wsgi > > WSGIScriptAlias /scripts/targeted_content /docs/content/scripts/ > > targeted_content.wsgi > > WSGIScriptAlias /scripts/refresh /docs/content/scripts/refresh.wsgi > > AddHandler xxx .wsgi and WSGIScriptAlias are intended to be > alternative ways of invoking WSGI scripts. I think you should not have > both for the same directory. -- 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.
