The allow_access() hook in mod_wsgi is only intended as a way of allowing or forbidding access base on host and nothing more.
To do anything more gets really complicated as you start to need a full blown Python wrapper for Apache's internal request object and hooking mechanism. The mod_python module did that, and I didn't specifically want to go down that path as it would have involved huge amounts of more work and make it much harder to maintain, with only a very small number of people even wanting it. Is there a specific reason you can't use mod_auth_tkt? If using Apache 2.4, have you looked at mod_session which is a part of Apache itself? Graham On 19/03/2014, at 9:23 PM, Jozef Vesely <[email protected]> wrote: > Hello, > > I am trying to implement something akin to mod_auth_tkt with mod_wsgi. > mod_auth_tkt intercepts apache access check hook to redirect user to login > page and set auth cookies. > > When I looked at mod_wsgi possibilities it seems that access hook's > response is limited to True/False. How do I redirect or set auth cookie > without access to response headers? > > I could do it as a wsgi middle-ware but I want it to work transparently for > any content served by apache: static files, cgi, php.... > (It would be possible to wrap those in the wsgi app as well but hey than I > don't need apache anymore...) > > Thanks for hints > > Jozef -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
