On Jan 31, 2008 2:49 PM, Steven Armstrong <[EMAIL PROTECTED]> wrote: > > Maybe something like this in your apache config? > > RedirectMatch permanent /(login|securepage) https://www.example.com/$1/ > > One idea is to redirect user login to HTTPS in same django apps but in different apache virtual than HTTP (80). This way two django instances would be running, that is why I don't want to use that method. Another thing is, i am not sure, but sessions will not be same for user in django when a user logins in HTTPS(443) and apps would not be able to use that session to recognize user on http(80). I would check the session implememtation in Django, if PORT number too is considered in generating session-id. Is there any thing, like initiating the SSL just for login on port 80 than changing it. -=Ravi=-
--~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
