Hi, I'm trying into integrate Shibboleth and Django running on WSGI. Briefly, Shib relies on an apache module that basically lays claim to the /Shibboleth.sso URL path, e.g. http://your.domain.tld/Shibboleth.sso/Metadata hosts your server's metadata, etc. But of course, django recommends the practice of setting WSGIScriptAlias / "/path/to/djanog.wsgi" in apache. So, my accesses to /Shibboleth.sso were getting re-routed to wsgi_module instead mod_shib. In fact, using this WSGI alias at the root there was no path where I could configure the shibboleth URL path to avoid wsgi_module, but this was of course the most convenient way to serve django without having to move a facsimile of urls.py into apache location directives.
So, although Alias directive allows serving static paths to take precedence over WSGIScriptAlias, it would still be nice to specify an opt-out of WSGIScriptAlias processing for a path under the specified one, in this case to hand the path over to another module. Does such an option exist? BTW I was able to find a work-around, which is to set 'Alias /Shibboleth.sso /tmp', while Alias taking precedence over WSGIScriptAlias and Shib taking precedence over the static file. But this solution feels dirty to me, so I'd really appreciate any opinions on the right way to do this, and whether this might make a reasonable feature request for the wsgi_module maintainers. Thanks, Jason -- 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/-/rKD1cipYe_MJ. 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.
