On 1 July 2011 07:48, Graham Dumpleton <[email protected]> wrote: > On 1 July 2011 01:33, James Slagle <[email protected]> wrote: >> >> >> On Jun 30, 7:55 am, Graham Dumpleton <[email protected]> >> wrote: >>> On 30 June 2011 21:46, James Slagle <[email protected]> wrote: >>> >>> > This isn't a wsgi application though, so I don't have access to >>> > environ via WSGIAccessScript, >>> >>> Yes you do. The first argument to allow_acess is an environ >>> dictionary. It is similar to what a WSGI application later gets but >>> doesn't have as much information in it. It should have the SSL >>> functions hooks. >>> >> >> The environ I get in check_password when using WSGIAuthUserScript does >> not have mod_ssl.is_https or mod_ssl.var_lookup in it. > > The you can't be using mod_wsgi 3.X which I said this feature is in. > You must be still using much older mod_wsgi 2.X. > > Version 3.0 of mod_wsgi was released a year and a half ago.
Okay, I am wrong. From mod_wsgi 4.0 change notes: 6. Access, authentication and authorisation hooks now have additional keys in the environ dictionary for 'mod_ssl.is_https' and 'mod_ssl.var_lookup'. These equate to callable functions provided by mod_ssl for determining if the client connection to Apache used SSL and what the values of variables specified in the SSL certifcates, server or client, are. These are only available if Apache 2.0 or later is being used. So you would have to use mod_wsgi from source code repository trunk. Graham -- 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.
