Ravi Kumar wrote on 01/31/08 12:07:
> 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.
If you want http and https you will need two virtual hosts. There is no
way around it. Maybe it's easier to just use https for everything.
I often use the following config:
<VirtualHost 1.2.3.4:80>
ServerName www.example.com
Redirect permanent / https://www.example.com/
</VirtualHost>
<VirtualHost 1.2.3.4:443>
... django and other config here ...
</VirtualHost>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
