[nag] once more: /nag/t/save
erling at eph.dk
erling at eph.dk
Sun Feb 3 19:13:41 UTC 2013
He he
Now to answer my ovwn question..
That thinking didn't implode my head.
I was puzled about why my http to https rewrite rule did its job while
hordes didn't.
My http to https rewrite rule is placed in httpd.conf on port *:80
as this:
<Location /horde>
RewriteEngine on
RewriteCond %{HTTPS} !^on$ [NC]
RewriteRule . https://%{HTTP_HOST}%{REQUEST_URI} [L]
</Location>
And this worked like a charm
So why not just ad the horde rule?
Like this:
<Location /horde>
RewriteEngine on
RewriteCond %{HTTPS} !^on$ [NC]
RewriteRule . https://%{HTTP_HOST}%{REQUEST_URI} [L]
RewriteBase /horde
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ rampage.php [QSA,L]
</Location>
Now it is all computing well. :-)
Cleanup sometimes helps a lot...
Thank and have a nice day
/erling
More information about the nag
mailing list