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

时间:2018-09-20 17:33:51

标签: apache .htaccess drupal https

我在我的网站上安装了安全证书,并希望强制所有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文件,以防出现问题,并且它没有格式化,而已安装的版本肯定更容易读起来很不错,带有中断等。我假设查看文件有一个窍门,所以它不会在一起处理,但是对此的任何见解将不胜感激!

**格式化的确是记事本-归功于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}]

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

2 个答案:

答案 0 :(得分: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}%{SERVER_PROTOCOL}

我不确定这是错误还是仅取决于apache版本的行为。这是一些调试或反复试验的地方。

除此之外,某些规则现在效率低下。让我们看一下:

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

这将检查请求是否通过常规HTTP发出,并且在这种情况下,它将以任何进入请求的ServerAlias重定向到https,并停止进一步处理([L])。这是重定向到规范版本的绝佳机会。

您仍然必须检查请求是否通过规范版本传入,以防万一,就像在代码段中所做的那样:

RewriteCond %{HTTP_HOST} !^www\.

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

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

答案 1 :(得分:0)

感谢您的帮助@msg。不幸的是,在我的情况下,我最终还是使用iis进行了重定向,我只注意到更新了settings.config。如果您对可能存在的连接有任何了解,我会很感兴趣的。