On 8 Oct 2006, at 5:27, [EMAIL PROTECTED] wrote: > so now we can specify our urls for, say a login screen, and enjoy > ssl for that page only without explicit redirects. Also there is no > way for a user to request an unsecure version of that page if one > is not explicitly offered.
Yes, unless they find a way to work around the middleware, that is ;-) This also means there is no ambiguity over the canonical URI of a page. I’m thinking about modifying the HTTPS_PATHS setting to accept regular expressions instead of just strings, that would allow for even more flexibility. I’m still thinking, though, maybe it’s overkill. Cheers. -- Antonio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
