我有一个带有Symfony 3的APACHE服务器，我想在不使用Symfony的情况下在域的根部上有一个主页。
当我加载http://website.com/api/requestparameters时，我可以获得我的API请求（因此在Symfony Bundle中）当我加载http://website.com/doc/时，我会降落在名为com.com/doc/api.html的页面上，存储在/doc/api.html中（所以我不去Symfony的事情）
但是，当我尝试加载http://website.com时，我无法到达index.html谁位于我的Web目录的根部！
所以我整天都在尝试制作捆绑包并创建一个路由，以便我可以在新捆绑包中使用我的index.html，并且路由会抓住网站。html.twig我终于成功了，但我意识到这不是我想要的，因为我将不得不对我的网站进行大量更改以将其转换为树枝（我的索引中有JavaScript和Angular东西...）
我觉得在htaccess可以做些事情，所以我尝试修改我的.htaccess（下面链接的原始）
当我设置DirectoryIndex index.html和RewriteEngine Off时，我的API不再起作用，但是可以访问我的HTML文件。
当我设置DirectoryIndex index.html并注释RewriteRule ^ %{ENV:BASE}/app.php [L]时，同一件事附加
仅设置DirectoryIndex index.html，不进行更改
- 问题是我不想使用树枝。
- 我觉得捆绑包不是我需要的，应该有另一种方法来做（我认为网站com.com/doc/api.html使用一个捆绑包，为什么要使用一个？）
.htaccess
# Use the front controller as index file. It serves as a fallback solution when
# every other rewrite/redirect fails (e.g. in an aliased environment without
# mod_rewrite). Additionally, this reduces the matching process for the
# start page (path "/") because otherwise Apache will apply the rewriting rules
# to each configured DirectoryIndex file (e.g. index.php, index.html, index.pl).
DirectoryIndex app.php
# By default, Apache does not evaluate symbolic links if you did not enable this
# feature in your server configuration. Uncomment the following line if you
# install assets as symlinks or if you experience problems related to symlinks
# when compiling LESS/Sass/CoffeScript assets.
# Options FollowSymlinks
# Disabling MultiViews prevents unwanted negotiation, e.g. "/app" should not resolve
# to the front controller "/app.php" but be rewritten to "/app.php/app".
<IfModule mod_negotiation.c>
Options -MultiViews
</IfModule>
<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}/$1 [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>
谢谢
它发生了，因为Apache从根/重定向到app.php（＃重写所有其他查询到前控制器。RewriteRule ^ %{ENV:BASE}/app.php [L]）
添加将root将root重写为 index.html
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^$ index.html [L]
...
</IfModule>