Ssl

如何從“https://www.example.com”重定向到“https://example.com”?

  • May 28, 2017

我想知道:

如何從..重定向

https://www.example.com

成為

https://example.com

通過.htaccess 或CPanel?

由於 SSL 只安裝在沒有“www”的那個上,當我訪問“www”那個時,我得到 SSL 錯誤。


整個 .htaccess 文件:

# Use PHP 5.3
AddType application/x-httpd-php53 .php

##
# @package      Joomla
# @copyright    Copyright (C) 2005 - 2012 Open Source Matters. All rights reserved.
# @license      GNU General Public License version 2 or later; see LICENSE.txt
##

##
# READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE!
#
# The line just below this section: 'Options +FollowSymLinks' may cause problems
# with some server configurations.  It is required for use of mod_rewrite, but may already
# be set by your server administrator in a way that dissallows changing it in
# your .htaccess file.  If using it causes your server to error out, comment it out (add # to
# beginning of line), reload your site in your browser and test your sef url's.  If they work,
# it has been set by your server administrator and you do not need it set here.
##

## Can be commented out if causes errors, see notes above.
Options +FollowSymLinks

## Mod_rewrite in use.

RewriteEngine On

## Begin - Rewrite rules to block out some common exploits.
# If you experience problems on your site block out the operations listed below
# This attempts to block the most common type of exploit `attempts` to Joomla!
#
# Block out any script trying to base64_encode data within the URL.
RewriteCond %{QUERY_STRING} base64_encode[^(]*\([^)]*\) [OR]
# Block out any script that includes a <script> tag in URL.
RewriteCond %{QUERY_STRING} (<|%3C)([^s]*s)+cript.*(>|%3E) [NC,OR]
# Block out any script trying to set a PHP GLOBALS variable via URL.
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
# Block out any script trying to modify a _REQUEST variable via URL.
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2})
# Return 403 Forbidden header and show the content of the root homepage
RewriteRule .* index.php [F]
#
## End - Rewrite rules to block out some common exploits.

## Begin - Custom redirects
#
# If you need to redirect some pages, or set a canonical non-www to
# www redirect (or vice versa), place that code here. Ensure those
# redirects use the correct RewriteRule syntax and the [R=301,L] flags.
#
## End - Custom redirects

##
# Uncomment following line if your webserver's URL
# is not directly related to physical file paths.
# Update Your Joomla! Directory (just / for root).
##

# RewriteBase /

## Begin - Joomla! core SEF Section.
#
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
#
# If the requested path and file is not /index.php and the request
# has not already been internally rewritten to the index.php script
RewriteCond %{REQUEST_URI} !^/index\.php
# and the request is for something within the component folder,
# or for the site root, or for an extensionless URL, or the
# requested URL ends with one of the listed extensions
RewriteCond %{REQUEST_URI} /component/|(/[^.]*|\.(php|html?|feed|pdf|vcf|raw))$ [NC]
# and the requested path and file doesn't directly match a physical file
RewriteCond %{REQUEST_FILENAME} !-f
# and the requested path and file doesn't directly match a physical folder
RewriteCond %{REQUEST_FILENAME} !-d
# internally rewrite the request to the index.php script
RewriteRule .* index.php [L]
#
## End - Joomla! core SEF Section.
<IfModule mod_headers.c>
Header unset ETag
#Header unset Last-Modified
</IfModule>
FileETag None
#<FilesMatch "\.(ico|gz|JPG|jpg|jpeg|png|gif|js|css|swf)$">
#Header unset Cache-control
#Header set Expires "access plus 1 month"
#</FilesMatch>

<FilesMatch "\.(?!(ico|gz|JPG|jpg|jpeg|png|gif|js|css|swf))[^.]+$">
 Header unset Last-Modified
 Header unset Cache-control
</FilesMatch>

# Google Analytics Integration - Added by cPanel.
<IfModule mod_substitute.c>
AddOutputFilterByType SUBSTITUTE text/html
Substitute "s|(<script src='/google_analytics_auto.js'></script>)?</head>|<script src='/google_analytics_auto.js'></script></head>|i"
</IfModule>
# END Google Analytics Integration

RewriteEngine On
RewriteCond %{HTTPS} OFF
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

RewriteCond %{HTTP_HOST} ^shop\.iravin\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.shop\.iravin\.com$
RewriteRule ^/?$ "https\:\/\/iravin\.com\/index\.php\?option\=com_virtuemart" [R=301,L]

您在同一個 IP 地址上擁有兩個域 (example.com和)。www.example.com然後,您為 HTTP 打開了埠 80,為 HTTPS 打開了埠 443。正如您所注意到的,該埠對伺服器上的所有域都是開放的;它不能只對一個域關閉,而對任何其他域保持開放。

當客戶端連接到https://www.example.com時,它將開始 SSL 協商,使用者將收到 SSL 證書不匹配的警告。您創建的任何重定向只會SSL 協商之後發生,因此他們仍然會收到 SSL 證書警告。

您應該獲得一個證書,該證書可以是萬用字元域證書(即匹配 的證書*.example.com)或具有www.example.com僅作為主題備用名稱的證書domain-name.com。這樣,兩者都www.example.com可以example.com在沒有警告的情況下工作。

這裡有更多關於 SSL 證書和網路伺服器的資訊:問:多個 SSL 域在同一個 IP 地址和同一個埠上?

引用自:https://serverfault.com/questions/510578