Drupal 7 .htaccess 文件不强制重定向到 HTTPS

Question

我在我的网站上安装了一个安全证书，并希望强制所有 URL 使用“https”以及“www”。我通过取消注释更新了 .htaccess：

RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

但是，在保存后，该站点并未强制执行 https 或 www。我清除了缓存，甚至重新启动了服务器，但仍然没有任何变化——所以我怀疑文件中的某个地方存在冲突，但也可能是其他问题。解决此问题以使重定向正常工作的最有效方法是什么？目前文件如下：

#
# Apache/PHP/Drupal settings:
#

# Protect files and directories from prying eyes.
<FilesMatch "\.(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl)(~|\.sw[op]|\.bak|\.orig|\.save)?$|^(\..*|Entries.*|Repository|Root|Tag|Template)$|^#.*#$|\.php(~|\.sw[op]|\.bak|\.orig\.save)$">
Order allow,deny
</FilesMatch>
# Don't show directory listings for URLs which map to a directory.
Options -Indexes

# Follow symbolic links in this directory.
Options +FollowSymLinks

# Make Drupal handle any 404 errors.
ErrorDocument 404 /index.php

# Set the default handler.
DirectoryIndex index.php index.html index.htm

# Override PHP settings that cannot be changed at runtime. See
# sites/default/default.settings.php and drupal_environment_initialize() in
# includes/bootstrap.inc for settings that can be changed at runtime.

# PHP 5, Apache 1 and 2.
<IfModule mod_php5.c>
php_flag magic_quotes_gpc                 off
php_flag magic_quotes_sybase              off
php_flag register_globals                 off
php_flag session.auto_start               off
php_value mbstring.http_input             pass
php_value mbstring.http_output            pass
php_flag mbstring.encoding_translation    off
</IfModule>

# Requires mod_expires to be enabled.
<IfModule mod_expires.c>
# Enable expirations.
ExpiresActive On

# Cache all files for 2 weeks after access (A).
ExpiresDefault A1209600

<FilesMatch \.php$>
# Do not allow PHP scripts to be cached unless they explicitly send cache
# headers themselves. Otherwise all scripts would have to overwrite the
# headers set by mod_expires if they want another caching behavior. This may
# fail if an error occurs early in the bootstrap process, and it may cause
# problems if a non-Drupal PHP file is installed in a subdirectory.
ExpiresActive Off
</FilesMatch>
</IfModule>

# Various rewrite rules.
<IfModule mod_rewrite.c>
RewriteEngine on

# Set "protossl" to "s" if we were accessed via https://.  This is used later
# if you enable "www." stripping or enforcement, in order to ensure that
# you don't bounce between http and https.
RewriteRule ^ - [E=protossl]
RewriteCond %{HTTPS} on
RewriteRule ^ - [E=protossl:s]

# Make sure Authorization HTTP header is available to PHP
# even when running as CGI or FastCGI.
RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

# Block access to "hidden" directories whose names begin with a period. This
# includes directories used by version control systems such as Subversion or
# Git to store control files. Files whose names begin with a period, as well
# as the control files used by CVS, are protected by the FilesMatch directive
# above.
#
# NOTE: This only works when mod_rewrite is loaded. Without mod_rewrite, it is
# not possible to block access to entire directories from .htaccess, because
# <DirectoryMatch> is not allowed here.
#
# If you do not have mod_rewrite installed, you should remove these
# directories from your webroot or otherwise protect them from being
# downloaded.
RewriteRule "(^|/)\." - [F]

# If your site can be accessed both with and without the 'www.' prefix, you
# can use one of the following settings to redirect users to your preferred
# URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
#
# To redirect all users to access the site WITH the 'www.' prefix,
# (http://example.com/... will be redirected to http://www.example.com/...)
# uncomment the following:
RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
#
# To redirect all users to access the site WITHOUT the 'www.' prefix,
# (http://www.example.com/... will be redirected to http://example.com/...)
# uncomment the following:
# RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
# RewriteRule ^ http%{ENV:protossl}://%1%{REQUEST_URI} [L,R=301]

# Modify the RewriteBase if you are using Drupal in a subdirectory or in a
# VirtualDocumentRoot and the rewrite rules are not working properly.
# For example if your site is at http://example.com/drupal uncomment and
# modify the following line:
# RewriteBase /drupal
#
# If your site is running in a VirtualDocumentRoot at http://example.com/,
# uncomment the following line:
# RewriteBase /

# Pass all requests not referring directly to files in the filesystem to
# index.php. Clean URLs are handled in drupal_environment_initialize().
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^ index.php [L]

# Rules to correctly serve gzip compressed CSS and JS files.
# Requires both mod_rewrite and mod_headers to be enabled.
<IfModule mod_headers.c>
# Serve gzip compressed CSS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.css $1\.css\.gz [QSA]

# Serve gzip compressed JS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.js $1\.js\.gz [QSA]

# Serve correct content types, and prevent mod_deflate double gzip.
RewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1]
RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1]

<FilesMatch "(\.js\.gz|\.css\.gz)$">
# Serve correct encoding type.
Header set Content-Encoding gzip
# Force proxies to cache gzipped & non-gzipped css/js files separately.
Header append Vary Accept-Encoding
</FilesMatch>
</IfModule>
</IfModule>

额外的问题（感谢您到此为止！）- 我下载了 Drupal 的副本以替换 htaccess 文件以防出现问题，并且它未格式化，而已安装的版本肯定更容易阅读，因为它的格式很好，带有中断等。我假设查看文件有一个技巧，因此它不会被压缩在一起 - 但任何对此的见解将不胜感激！

**格式化确实是记事本——一旦进入 sublime，它就可以按预期工作，这要归功于 msg。

**更新问题：

谢谢你的消息 - 所以有了你关于开箱即用的评论，我决定重新下载相同版本的 Drupal 并复制 htaccess 文件，然后像以前一样取消注释，并在“RewriteEngine”下方添加 3 行代码" - www 现在可以正常工作，但使用安全的力量仍然没有。相关代码部分（据我所知）是：

# Various rewrite rules.
<IfModule mod_rewrite.c>
RewriteEngine on

RewriteCond %{HTTPS} off
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# Set "protossl" to "s" if we were accessed via https://.  This is used later
# if you enable "www." stripping or enforcement, in order to ensure that
# you don't bounce between http and https.
RewriteRule ^ - [E=protossl]
RewriteCond %{HTTPS} on
RewriteRule ^ - [E=protossl:s]

# Make sure Authorization HTTP header is available to PHP
# even when running as CGI or FastCGI.
RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

添加的行是否可能与未注释的其他代码冲突？

Answer 1

默认的 .htaccess 应该开箱即用，所以我将从清单开始：

• 验证 mod_rewrite 是否已加载：apache2ctl -D DUMP_MODULES
• 确保 .htaccess 文件未被禁止：服务器配置中没有 AllowOverride None。
• Enable rewrite log

至于格式，看起来编辑器没有正确显示换行符。记事本有机会吗？

编辑：再看一遍，这实际上并没有重定向到页面的 https 版本，只是确保保持与原始请求相同的协议。尝试在RewriteEngine on 之后添加这个：

RewriteCond %{HTTPS} off
RewriteRule ^ https://www.yoursitehere.com [R,L]

EDIT2：它不应该，但我有几点需要指出：

• X-Forwarded-Proto 如果未设置，可能会导致问题。如果您没有负载均衡器或代理，请尝试将其注释掉。
• 我有时会遇到未设置%{HTTPS} 的情况，我求助于使用%{SERVER_PORT} o %{SERVER_PROTOCOL}。

我不确定这是一个错误还是仅仅是依赖于 apache 版本的行为。这就是一些调试或试错的地方。

除此之外，一些规则现在有点低效。让我们看看：

RewriteCond %{HTTPS} off
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

这会检查请求是否通过常规 HTTP 来，如果是，它会重定向到 https 中的任何 ServerAlias 请求，并停止进一步处理 ([L])。这是重定向到规范版本的绝佳机会。

您仍然需要检查请求是否通过规范版本进入，以防万一，因为它在块中完成：

RewriteCond %{HTTP_HOST} !^www\.

这将导致客户端另一个重定向。

或者您可以将 Cond 与我们的 [OR] 标志结合起来并完成。

Answer 2

感谢您的帮助@msg。不幸的是，在我的情况下，我最终最终使用 iis 来重定向，我注意到只更新了 settings.config。如果您对可能存在的联系有任何见解，我会非常有兴趣听到它。