2015-12-26 35 views
0

我想更新一个旧的Web应用程序,所以我试图设置遗留应用程序和并行的更新版本,并逐步迁移到新的。
旧的应用程序直接位于下的public_html,并且已经把下的新应用程序的public_html/symsale,现在我要定向到新应用程序的所有请求被重写后symsale增加了网络子目录,即:像/symsale/path这样的网址,必须重写为/symsale/web/path。为此,我创建了一个.htaccess文件并将其置于symsale目录下。内容如下:麻烦重定向到使用Apache的`mod_rewrite`子目录

<IfModule mod_rewrite.c> 
    RewriteEngine On 

    RewriteRule ^(.*)(symsale)(.*)$ $1$2/web$3 [L] # i've tried it both with and without the 'L' 
</IfModule> 

当我尝试导航到/symsale/我得到以下错误

您没有权限访问/ symsale /在此服务器上。

但是,当我使用/symsale/web来代替时,它工作得很好。这里有什么问题?

:我已经看到了这些其他问题:Apache rewrite rule to redirect all request to subdirectory containing another .htaccess and rewrite rulesApache RewriteRule to subdirectory.htaccess rewrite to redirect root URL to subdirectory

:我使用symfony框架(PHP),所以还有另外一个.htaccess文件网内文件夹,该文件夹将所有路由重写到前端控制器。下面的内容是.htaccess

的DirectoryIndex app.php

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

<IfModule !mod_rewrite.c> 
    <IfModule mod_alias.c> 
     # When mod_rewrite is not available, we instruct a temporary redirect of 
     # the start page to the front controller explicitly so that the website 
     # and the generated links can still be used. 
     RedirectMatch 302 ^/$ /app.php/ 
     # RedirectTemp cannot be used instead 
    </IfModule> 
</IfModule> 

回答

0

这里是一个跳槽 - mod_rewrite的有一个不幸/古怪的行为在那里猜测,无论您是代一个文件系统路径或URL路径。它通过查看替换的第一个组件并查看其是否存在磁盘上的目录(绝对路径)来猜测。

您碰巧在文件系统的根目录中有/ symsale /?我相信[PT]会将这种猜测短路并迫使结果被视为URI。

+0

我的文件系统中没有'/ symsale /'。但我认为你所说的话可能会持续,因为否则它会给'symsale'而不是'/ symsale /'(我认为)带来一些错误。什么是[PT]? – user2268997