2015-12-21 111 views
1

我已经在CentOS 7虚拟盒子上运行了symfony 2.8。现在,当我尝试去我的网站时,我得到一个内部服务器错误。当我检查了日志,它说:Symfony导致mod_rewrite重定向错误

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

我有LogLevel Apache中设置为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(不要担心任何安全问题这是一个本地安装仅dev的目的)

# 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" 

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

回答

0

改变你的最后RewriteRule这样:

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

这导致404找不到app.php – LoneWolfPR

+1

这只是意味着'%{ENV:BASE}/app.php'(即'app.php '在当前目录中)不存在。 – anubhava

+0

好的。我有一个怀疑,可能不会试图从正确的文档根目录拉。我怎么知道它试图从app.php中提取? – LoneWolfPR