On 26-Mar-09, at 11:54 AM, Ryan Kelly wrote:
> I'm trying to set things up so that my login form uses SSL to > protect the user's password in transit. Basically, the behaviour > I'm after is as follows: > > 1) Unauthenticated user requests http://site/private/ > 2) They're redirected to http://site/login/ > 3) They submit their details securely to https://site/login/ > 4) This establishes the login and redirects to http://site/private/ I have used, in a project before, a *third-party* SSL Middleware[0] to effectively achieve what you are after. I won't comment further, apart from saying that it has worked a treat for my requirements. You may peruse the source and the brief yet to the point documentation describing how to use it. [0] http://www.djangosnippets.org/snippets/85/ -- Ayaz Ahmed Khan An evil mind is a great comfort. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
