Ivan Sagalaev wrote: > 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.
I'll have to look at it in more detail but it looks close to what I want. It does leave one thing out though--creating a 401 response if authentication is missing. > 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 ;-) Since I'm brand new at this I haven't got the faintest what you're talking about here. Pointers are welcome :-) /M --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
