麻煩重定向到使用Apache的`mod_rewrite`子目錄

Question

我想更新一箇舊的Web應用程序，所以我試圖設置遺留應用程序和並行的更新版本，並逐步遷移到新的。
舊的應用程序直接位於下的public_html，並且已經把下的新應用程序的public_html/symsale，現在我要定向到新應用程序的所有請求被重寫後symsale增加了網絡子目錄，即：像/symsale/path這樣的網址，必須重寫爲/symsale/web/path。爲此，我創建了一個.htaccess文件並將其置於symsale目錄下。內容如下：

<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 rules，Apache 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> 

Answer 1

這裏是一個跳槽 - mod_rewrite的有一個不幸/古怪的行爲在那裏猜測，無論您是代一個文件系統路徑或URL路徑。它通過查看替換的第一個組件並查看其是否存在磁盤上的目錄（絕對路徑）來猜測。

您碰巧在文件系統的根目錄中有/ symsale /？我相信[PT]會將這種猜測短路並迫使結果被視爲URI。