【问题标题】:Symfony causing redirect error with mod_rewriteSymfony 使用 mod_rewrite 导致重定向错误
【发布时间】:2016-03-27 17:45:31
【问题描述】:

我在 CentOS 7 虚拟机上运行了 symfony 2.8。现在,当我尝试访问我的站点时,出现内部服务器错误。当我检查日志时,它说:

Request exceeded the limit of 10 internal redirects due to probable configuration error

我将 apache 中的 LogLevel 设置为 trace3,看起来 app.php 周围有一大堆重定向。我不确定发生了什么。我没有修改 symfony 附带的 .htaccess 文件。这是我的 .htaccess 文件中的 mod_rewrite 块:

<IfModule mod_rewrite.c>
    RewriteEngine On

    # Determine the RewriteBase automatically and set it as environment variable.
    # If you are using Apache aliases to do mass virtual hosting or installed the
    # project in a subdirectory, the base path will be prepended to allow proper
    # resolution of the app.php file and to redirect to the correct URI. It will
    # work in environments without path prefix as well, providing a safe, one-size
    # fits all solution. But as you do not need it in this case, you can comment
    # the following 2 lines to eliminate the overhead.
    RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]

    # Sets the HTTP_AUTHORIZATION header removed by apache
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect to URI without front controller to prevent duplicate content
    # (with and without `/app.php`). Only do this redirect on the initial
    # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
    # endless redirect loop (request -> rewrite to front controller ->
    # redirect -> request -> ...).
    # So in case you get a "too many redirects" error or you always get redirected
    # to the start page because your Apache does not expose the REDIRECT_STATUS
    # environment variable, you have 2 choices:
    # - disable this feature by commenting the following 2 lines or
    # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
    #   following RewriteCond (best solution)
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
    RewriteRule ^app\.php(/(.*)|$) %{ENV:BASE}/$2 [R=301,L]

    # If the requested filename exists, simply serve it.
    # We only want to let Apache serve files and not directories.
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteRule .? - [L]

    # Rewrite all other queries to the front controller.
    RewriteRule .? %{ENV:BASE}/app.php [L]
</IfModule>

这是我的 httpd.conf(不用担心任何安全问题。这只是用于开发目的的本地安装)

# Security
ServerTokens OS
ServerSignature On
TraceEnable On

ServerName "dev.indygaa.vm"
ServerRoot "/etc/httpd"
PidFile run/httpd.pid
Timeout 120
KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimeout 15


User apache
Group apache

AccessFileName .htaccess
<FilesMatch "^\.ht">
    Require all denied
</FilesMatch>

<Directory />
  Options FollowSymLinks
  AllowOverride All
</Directory>


HostnameLookups Off
ErrorLog "/var/log/httpd/error_log"
LogLevel trace3
EnableSendfile On

#Listen 80


Include "/etc/httpd/conf.d/*.load"
Include "/etc/httpd/conf/ports.conf"

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

IncludeOptional "/etc/httpd/conf.d/*.conf"

我看不到这个重定向一直在哪里发生。我错过了什么?

【问题讨论】:

    标签: php .htaccess mod-rewrite apache2 symfony-2.8


    【解决方案1】:

    将您的最后一个 RewriteRule 更改为:

    RewriteRule !/app\.php$ %{ENV:BASE}/app.php [L,NC]
    

    【讨论】:

    • 导致 404 Not Found for app.php
    • 这只是意味着%{ENV:BASE}/app.php(即当前目录中的app.php)不存在。
    • 好的。我怀疑可能没有尝试从正确的文档根目录中提取。我怎么知道它试图从哪里拉 app.php?
    • 如果app.php.htaccess 存在于同一文件夹中,则可以尝试:RewriteRule !^app\.php$ app.php [L,NC]
    • 哦,好吧,那么最好使用正确的已知路径而不是%{ENV:BASE}
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2014-06-20
    • 2016-01-18
    • 2012-03-18
    相关资源
    最近更新 更多