Dear Wiki user, You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.
The following page has been changed by pctony: http://wiki.apache.org/httpd/ScratchPad/RedirectSSL ------------------------------------------------------------------------------ + Describe ScratchPad/RedirectSSL here. - Pepper: - = Redirect Request to SSL = - Let's say you want http://www.domain.com/secure/ to always be sent over SSL (I presume here that both the normal and the SSL vhost have the same content). You could do this by linking to the correct page from within your HTML pages... but there will always be some user who will sneak by it that way. - - == Using mod_rewrite == - {{{ - <Location /secure> - RewriteEngine On - ReWriteCond %{HTTPS} !=on - RewriteRule .* https://%{HTTP_HOST}:8443%{REQUEST_URI} [QSA,R=permanent,L] - </Location> - }}} - - '''Note: This snippet can also be used inside a directory or vhost container. If the SSL port is 443 (the default), you don't need it (or the colon) in the RewriteRule, as all browsers which support SSL will automatically use port 443; this example redirects to an SSL server on port 8443.''' - - Make sure you have loaded [http://httpd.apache.org/docs/trunk/mod/mod_rewrite.html mod_rewrite] and have it enabled. - - {{{ - LoadModule rewrite_module modules/mod_rewrite.so - RewriteEngine On - }}} - - == Using virtual hosts == - - When using SSL, you will frequently have at least two virtual hosts: one on port 80 to serve ordinary requests, and one on port 443 to serve SSL. If you wish to redirect users from the non-secure site to the SSL site, you can use an ordinary [http://httpd.apache.org/docs/trunk/mod/mod_alias.html#redirect Redirect] directive inside the non-secure VirtualHost: - - {{{ - NameVirtualHost *:80 - <VirtualHost *:80> - ServerName mysite.example.com - DocumentRoot /usr/local/apache2/htdocs - Redirect permanent /secure https://mysite.example.com/secure - </VirtualHost> - - <VirtualHost _default_:443> - ServerName mysite.example.com - DocumentRoot /usr/local/apache2/htdocs - SSLEngine On - # etc... - </VirtualHost> - }}} - - - - == Most Secure SSL Redirect Method (doesn't require mod_rewrite!) == - This will check to make sure that the connection is using SSL, or it will fail. This works whether you are serving SSL on port 443, 80, 81, or elsewhere. This is the most secure setting for SSL logins. - - This also avoids having to type in the username and password twice by requiring the HTTP_HOST to match the HTTP_HOST that your SSL certificate is set up for; in the case above, the certificate is for `askapache.com` rather than `www.askapache.com` - - So if either of those 2 checks fail '''(no SSL or incorrect domain)''' then the (403) ErrorDocument directive redirects the browser to try again at https://askapache.com . - {{{ - [IfModule mod_ssl.c] - SSLOptions +StrictRequire - SSLRequireSSL - SSLRequire %{HTTP_HOST} eq "askapache.com" - ErrorDocument 403 https://askapache.com - [/IfModule] - }}} - - - == Rewrite non-SSL requests to SSL with `mod_rewrite` == - {{{ - [IfModule !mod_rewrite.c] - RewriteCond %{HTTPS} !=on - RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [QSA,R=301,L] - [/IfModule] - }}} - ''NOTE'': The ''HTTPS'' variable is always present, even if `mod_ssl` isnât loaded! This is useful if a non-SSL server is redirecting to a different SSL-enabled server. - - - == Redirect everything served on port 80 to SSL == - {{{ - RewriteCond %{SERVER_PORT} ^80$ - RewriteRule ^.*$ https://%{HTTP_HOST}%{REQUEST_URI} [QSA,R=301,L] - }}} - - - == Changing to SSL or non-SSL using relative URLs == - {{{ - RewriteRule ^/(.*):SSL$ https://%{SERVER_NAME}/$1 [QSA,R,L] - RewriteRule ^/(.*):NOSSL$ http://%{SERVER_NAME}/$1 [QSA,R,L] - }}} - This lets you use URIs like: - {{{ - /document.html:SSL --> https://askapache.com/document.html - /document.html:NOSSL --> http://askapache.com/document.html - }}} -
