I'm trying to mix both static content (or content from other types
of handlers) with mod_wsgi handlers. I don't want to partition
things out into separate directories (like /static and /wsgiscripts),
but want them all to intermingle.
Through a variety of AddHandler and DirectoryIndex directives
I can get close. However I'm used to the mod_python feature
where it was pretty easy to make a SetHandler rule that would
get called for all URLs, regardless if there was actually a
file to map to. E.g., I could pop this into an .htaccess:
# Example in mod_python
SetHandler mod_python
PythonHandler mysitehandler::handler
<Files ~ "\.(css|js|png|jpg|txt|pdf)$">
SetHandler None
</Files>
However with mod_wsgi, the only thing I'm lacking is something
equivalent to the "PythonHandler". So when the SetHandler wsgi-script
is in effect, it tries to use the URL as the path to the WSGI script,
rather then letting me pick a specific script to use.
I'm not having much luck trying to do something similar to how
I've used mod_python. Close, but I still seem to have holes.
I'd like something that I can use at the .htaccess level if possible.
Does anybody know what I'm missing?
--
Deron Meranda
--
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.
