I've made some progress.
I first attempted to put "WSGIVerboseDebugging On" in the VirtualHost
section of my configuration and Apache complained on startup. OK, so I
moved that out of the VirtualHost. That made me realize that VirtualHost
might be special in some way (as far as mod_wsgi is concerned). Turns out
that it was special, because placing the WSGI commands outside of the
VirtualHost section made it work normally. So it appears that something
might be up with the way mod_wsgi handles the alias in Apache 2.4.3 on
Windows. Additionally, it doesn't give any errors (even with debug output
on), it just fails to recognize the alias.
----------------------------------------
Works
----------------------------------------
LoadModule wsgi_module modules/mod_wsgi.so
WSGIScriptAlias /flask "/Apache24/wsgi/flask/wsgihandler.wsgi"
<Directory "/Apache24/wsgi/flask">
AllowOverride None
Options None
Require all granted
</Directory>
----------------------------------------
Doesn't Work
----------------------------------------
LoadModule wsgi_module modules/mod_wsgi.so
<VirtualHost *:80>
WSGIScriptAlias /flask "/Apache24/wsgi/flask/wsgihandler.wsgi"
<Directory "/Apache24/wsgi/flask">
AllowOverride None
Options None
Require all granted
</Directory>
</VirtualHost>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/modwsgi/-/-f1GQfwNyz8J.
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.
