Re: [EMAIL PROTECTED] ssl - force ssl per directory

2006-12-13 Thread Joshua Slive
On 12/12/06, Nathan Kellogg [EMAIL PROTECTED] wrote: We have open ssl running fine on Apache 2.2.3. A separate virtual host is defined for both the :80 port and for :443 In order that the .../secure/... directory be handled exclusively by the SSL host, we have : See:

Re: [EMAIL PROTECTED] ssl - force ssl per directory

2006-12-13 Thread Gregor Schneider
My suggestion: VirtualHost *:80 ServerName your_server ServerAdmin [EMAIL PROTECTED] # don't loose time with IP address lookups HostnameLookups Off # needed for named virtual hosts UseCanonicalName Off # RewriteEngine On RewriteRule ^/(.*)$ https://%{HTTP_HOST}/$1

[EMAIL PROTECTED] ssl - force ssl per directory

2006-12-12 Thread Nathan Kellogg
We have open ssl running fine on Apache 2.2.3. A separate virtual host is defined for both the :80 port and for :443 In order that the .../secure/... directory be handled exclusively by the SSL host, we have : in the :80 vhost : Redirect permanent c:/orcourt/htdocs/secure

Re: [EMAIL PROTECTED] ssl - force ssl per directory

2006-12-12 Thread Steve Swift
You are specifying a file in your redirect. My documentation states: Syntax: Redirect [status] URL-path URL The old URL-path is a (%-decoded) path beginning with a slash. A relative path is not allowed. On 12/12/06, Nathan Kellogg [EMAIL PROTECTED] wrote: We have open ssl running fine on