.htaccess URL重写和SSL冲突

我面临以下问题

使用

.htaccess

重写URL在HTTP URL上工作得非常好。 现在我已经在我的服务器上安装了

SSL证书

，现在可以使用HTTPS URL访问我的站点。网站可以正常使用普通URL，即

.htaccess

中没有URL重写规则的URL

但是当我访问一个HTTPS URL时，

.htaccess

中有一条规则，它会给我

404

错误

我已经执行了很多测试，比如简单的重定向到，但它不起作用

HTTPS URL似乎完全忽略了

.htaccess

文件中编写的规则和条件

请帮帮我

更多信息：

我的.htaccess代码是

Options +FollowSymLinks
RewriteEngine On
RewriteBase /

RewriteCond %{REQUEST_URI} !(/$|\.) 
RewriteRule (.*) %{REQUEST_URI}/ [R=301,L] 


RewriteCond %{REQUEST_FILENAME} !\.(pdf|js|ico|gif|jpg|png|css|rar|zip|tar\.gz)$
RewriteRule ^([^/]*)/([^/]*)$ index.php?%{QUERY_STRING}&current_event=$1 [L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d [OR]
RewriteCond %{REQUEST_URI} ^/$
RewriteCond %{REQUEST_FILENAME} !\.(pdf|js|ico|gif|jpg|png|css|rar|zip|tar\.gz)$
RewriteRule ^(.*)$ /commingsoon/index.html/$1 [L,QSA] 

我的服务器的指令文件的代码如下

ServerAdmin webmaster@localhost
ServerName www.mysite.com
ServerAlias mysite.com

DocumentRoot /var/www/mysite

<Directory />
    Options FollowSymLinks
    AllowOverride all
</Directory>
    <Directory /var/www/mysite>
            Options Indexes FollowSymLinks MultiViews
            AllowOverride all
            Order allow,deny
            allow from all
    </Directory>

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
<Directory "/usr/lib/cgi-bin">
    AllowOverride None
    Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
    Order allow,deny
    Allow from all
</Directory>

ErrorLog ${APACHE_LOG_DIR}/error.log

# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on

#   A self-signed (snakeoil) certificate can be created by installing
#   the ssl-cert package. See
#   /usr/share/doc/apache2.2-common/README.Debian.gz for more info.
#   If both key and certificate are stored in the same file, only the
#   SSLCertificateFile directive is needed.
    #   SSLCertificateFile    /etc/ssl/certs/ssl-cert-snakeoil.pem
    #   SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
    SSLCACertificateFile  /etc/ssl/private/ca_root.pem
    SSLCertificateChainFile /etc/ssl/private/intermediate.pem
    SSLCertificateFile    /etc/ssl/private/www.mysite.com.crt
    SSLCertificateKeyFile /etc/ssl/private/www.mysite.com.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
#   Note: Inside SSLCACertificatePath you need hash symlinks
#         to point to the certificate files. Use the provided
#         Makefile to update the hash symlinks after changes.
#SSLCACertificatePath /etc/ssl/certs/
#SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

#   Certificate Revocation Lists (CRL):
#   Set the CA revocation path where to find CA CRLs for client
#   authentication or alternatively one huge file containing all
#   of them (file must be PEM encoded)
#   Note: Inside SSLCARevocationPath you need hash symlinks
#         to point to the certificate files. Use the provided
#         Makefile to update the hash symlinks after changes.
#SSLCARevocationPath /etc/apache2/ssl.crl/
#SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

#   Client Authentication (Type):
#   Client certificate verification type and depth.  Types are
#   none, optional, require and optional_no_ca.  Depth is a
#   number which specifies how deeply to verify the certificate
#   issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth  10

#   Access Control:
#   With SSLRequire you can do per-directory access control based
#   on arbitrary complex boolean expressions containing server
#   variable checks and other lookup directives.  The syntax is a
#   mixture between C and Perl.  See the mod_ssl documentation
#   for more details.
#<Location />
#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
#           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>

#   SSL Engine Options:
#   Set various options for the SSL engine.
#   o FakeBasicAuth:
#     Translate the client X.509 into a Basic Authorisation.  This means that
#     the standard Auth/DBMAuth methods can be used for access control.  The
#     user name is the `one line' version of the client's X.509 certificate.
#     Note that no password is obtained from the user. Every entry in the user
#     file needs this password: `xxj31ZMTZzkVA'.
#   o ExportCertData:
#     This exports two additional environment variables: SSL_CLIENT_CERT and
#     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
#     server (always existing) and the client (only existing when client
#     authentication is used). This can be used to import the certificates
#     into CGI scripts.
#   o StdEnvVars:
#     This exports the standard SSL/TLS related `SSL_*' environment variables.
#     Per default this exportation is switched off for performance reasons,
#     because the extraction step is an expensive operation and is usually
#     useless for serving static content. So one usually enables the
#     exportation for CGI and SSI requests only.
#   o StrictRequire:
#     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
#     under a "Satisfy any" situation, i.e. when it applies access is denied
#     and no other module can change it.
#   o OptRenegotiate:
#     This enables optimized SSL connection renegotiation handling when SSL
#     directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<FilesMatch "\.(cgi|shtml|phtml|php)$">
    SSLOptions +StdEnvVars
</FilesMatch>
<Directory /usr/lib/cgi-bin>
    SSLOptions +StdEnvVars
</Directory>

#   SSL Protocol Adjustments:
#   The safe and default but still SSL/TLS standard compliant shutdown
#   approach is that mod_ssl sends the close notify alert but doesn't wait for
#   the close notify alert from client. When you need a different shutdown
#   approach you can use one of the following variables:
#   o ssl-unclean-shutdown:
#     This forces an unclean shutdown when the connection is closed, i.e. no
#     SSL close notify alert is send or allowed to received.  This violates
#     the SSL/TLS standard but is needed for some brain-dead browsers. Use
#     this when you receive I/O errors because of the standard approach where
#     mod_ssl sends the close notify alert.
#   o ssl-accurate-shutdown:
#     This forces an accurate shutdown when the connection is closed, i.e. a
#     SSL close notify alert is send and mod_ssl waits for the close notify
#     alert of the client. This is 100% SSL/TLS standard compliant, but in
#     practice often causes hanging connections with brain-dead browsers. Use
#     this only for browsers where you know that their SSL implementation
#     works correctly.
#   Notice: Most problems of broken clients are also related to the HTTP
#   keep-alive facility, so you usually additionally want to disable
#   keep-alive for those clients, too. Use variable "nokeepalive" for this.
#   Similarly, one has to force some clients to use HTTP/1.0 to workaround
#   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
#   "force-response-1.0" for this.
BrowserMatch "MSIE [2-6]" \
    nokeepalive ssl-unclean-shutdown \
    downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepalive
BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

ServerAdminwebmaster@localhost
服务器名www.mysite.com
服务器别名mysite.com
DocumentRoot/var/www/mysite
选项如下符号链接
允许超越所有
选项索引跟随符号链接多视图
允许超越所有
命令允许，拒绝
通融
ScriptAlias/cgi-bin//usr/lib/cgi-bin/
不允许超限
选项+执行CGI-多视图+符号链接所有者匹配
命令允许，拒绝
通融
ErrorLog${APACHE_LOG_DIR}/error.LOG
#可能的值包括：调试、信息、通知、警告、错误、临界值、，
#警惕，埃默格。
日志级别警告
CustomLog${APACHE\u LOG\u DIR}/ssl\u access.LOG组合
#SSL引擎交换机：
#为此虚拟主机启用/禁用SSL。
斯伦金安
#通过安装，可以创建自签名（snakeoil）证书
#ssl证书包。看见
#/usr/share/doc/apache2.2-common/README.Debian.gz了解更多信息。
#如果密钥和证书都存储在同一个文件中，则只有
#需要SSLCertificateFile指令。
#SSLCertificateFile/etc/ssl/certs/ssl-cert-snakeoil.pem
#SSLCertificateKeyFile/etc/ssl/private/ssl-cert-snakeoil.key
SSLCACertificateFile/etc/ssl/private/ca_root.pem
SSLCertificateChainFile/etc/ssl/private/intermediate.pem
SSLCertificateFile/etc/ssl/private/www.mysite.com.crt
SSLCertificateKeyFile/etc/ssl/private/www.mysite.com.key
#服务器证书链：
#将SSLCertificateChainFile指向包含
#PEM编码CA证书的串联，这些证书构成
#服务器证书的证书链。或者
#引用的文件可以与SSLCertificateFile相同
#将CA证书直接附加到服务器时
#方便证书。
#SSLCertificateChainFile/etc/apache2/ssl.crt/server-ca.crt
#证书颁发机构（CA）：
#设置要查找CA的CA证书验证路径
#用于客户端身份验证的证书，或者一个
#包含所有这些内容的大型文件（文件必须是PEM编码的）
#注意：在SSLCACertificatePath中，您需要哈希符号链接
#指向证书文件。使用提供的
#Makefile在更改后更新哈希符号链接。
#SSLCACertificatePath/etc/ssl/certs/
#SSLCACertificateFile/etc/apache2/ssl.crt/ca-bundle.crt
#证书吊销列表（CRL）：
#设置要在其中查找客户端的CA CRL的CA吊销路径
#身份验证，或者一个包含所有
#其中（文件必须为PEM编码）
#注意：在sslcareconcationpath中，您需要哈希符号链接
#指向证书文件。使用提供的
#Makefile在更改后更新哈希符号链接。
#sslcavocationpath/etc/apache2/ssl.crl/
#sslcaverocationfile/etc/apache2/ssl.crl/ca-bundle.crl
#客户端身份验证（类型）：
#客户端证书验证类型和深度。类型是
#无、可选、必需和可选。深度为
#指定证书验证深度的数字
#确定证书无效之前的颁发者链。
#SSLVerifyClient要求
#SSLVerifyDepth 10
#访问控制：
#使用SSLRequire，您可以基于
#关于包含服务器的任意复杂布尔表达式
#变量检查和其他查找指令。语法是
#C和Perl之间的混合。请参阅mod_ssl文档
#更多细节。
#
#SSLRequire（%%{SSL_CIPHER}！~m/^（EXP|NULL）/\
#以及%{SSL_CLIENT_S_DN_O}eq“蛇油有限公司”\
#和{“Staff”、“CA”、“Dev}中的%{SSL_CLIENT_S_DN_OU}\
#和%{TIME\u WDAY}>=1和%{TIME\u WDAY}=8和%{TIME\u HOUR}你能发布你的.htaccess文件吗？@Zorayr请检查，我已经更新了我的问题的更多细节。有一个类似的问题，你解决了吗？我自己做了很多尝试，但由于我是程序员而不是服务器管理员，所以我失败了。然后我问了一位Linux专家，他解决了这个问题