magus wrote:
> 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.
Ah... Yes, I have it in another place since I have a mixed
authorization. But it's simple to add where it checks
if not authorization:
return
it should be:
if not authorization:
from django.http import HttpResponse
response=HttpResponse()
response.status_code=401
response['WWW-Authenticate']='Basic realm="Your realm"'
return response
And you should also remove first to lines checking for
request.user.is_anonymous since you don't have request.user at this time.
>> 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 :-)
It's not related to your question exactly... Django recently learned to
use pluggable authorization modules for different authorization schemes
instead of built-in one. So I noted that this thing working as a
middleware should actually be such a module. It would be more clean
architecturally. But it still works :-)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
