In http://code.djangoproject.com/ticket/3583 I've added a patch which refactors the existing mod_python authentication function and adds a new cookie based one.
If anyone can, a review would be good. Specifically: 1. Does it work correctly for you? (it does for me) 2. Is the change in patch 2 a smart idea? 3. Is there anything I'm missing? The only step better than this would be a full PythonHandler which would return a redirect response to a log in page (specified by a PythonOption?) if the user isn't authenticated or doesn't have the correct permissions, otherwise it can just return apache.DECLINED, since the mod_python docs say: Where that final status is apache.DECLINED, Apache will fall back to using the default-handler and attempt to serve up the target as a static file. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
