Waylan Limberg wrote:
> Hmm, I guess I would create a separate "view" which does not have any > url mapped to it. As it is not available publicly (over http), do you > really need any other authentication than the systems file > permissions? Of course, you may need to write a little more code to > make sure everything is available that you would normally get via an > http request but that shouldn't be to difficult. I was intending that the e-mail wasn't recieved on the same machine as the blog is served from. Hence the http step. Ivan Sagalaev wrote : > You can use HTTP Authorization for this. In one of my projects I need to > handle not only clients with regular browsers but also download managers > for which redirects to the login view would be useless. I've made a > small middleware (attached) that does HTTP authorization. It works after > standard Django's authorization and checks if user is already > authenticated that way and if not tries HTTP auth. That sounds interesting. I'll take a look see if it fits. Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
