magus wrote: > Well, the auth module _requires_ the session stuff. Which in this case > is overkill. All I really need is to return a 401 and get a basic > authentication.
I've posted some time ago on this list a simple middleware that does HTTP authorization and sets request.user just like standard cookie-based authorization: http://groups.google.com/group/django-users/browse_thread/thread/cc928718a1a6cad5/201b8bed2315fb99?lnk=gst&rnum=1#201b8bed2315fb99 Looks like it'll work for you, even without modifications. However, more properly would be refactor it as an auth backend but I wrote it before multi-auth branch and now I'm too lazy ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
