如何在XAMPP 3.3.2中为Symfony 4项目配置虚拟主机

本文概述

• A.使用.htaccess
• B.没有.htaccess

在开始使用XAMPP在本地Symfony 4中进行开发之后, 由于我为项目配置了虚拟主机, 因此我遇到了一些路由问题。该错误通知我, 该错误不是在Symfony中, 而是在我的本地开发环境中为apache(我的vhost)配置的, 因为调试栏未正确加载, 并且始终收到消息：” Symfony 4：错误加载Web调试工具栏时发生”。我也注意到, 没有异常, 但是服务器消息”在此服务器上未找到”。

然后, 在阅读symfony的官方文档之后, .htaccess文件也进行了很多更改(默认情况下, 除非你为symfony安装了特殊的apache模块, 否则该文件不存在)。

第一种选择是创建此.htaccess文件, 在你的项目中安装带有composer的模块, 并为此配置虚拟主机。第二个选项是完全禁用虚拟主机中.htaccess的使用, 并在其上编写所有规则和指令。在本文中, 我们将向你展示如何在xampp安装中同时使用这两个选项

A.使用.htaccess

如果你愿意使用.htaccess文件重写指令等, 请使用以下命令继续在Symfony 4项目中安装symfony / apache-pack软件包：

composer require symfony/apache-pack

安装之后, 这将在你的项目/公共目录中创建一个.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 index.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. "/index" should not resolve
# to the front controller "/index.php" but be rewritten to "/index.php/index".
<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 index.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 `/index.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 ^index\.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}/index.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 307 ^/$ /index.php/
        # RedirectTemp cannot be used instead
    </IfModule>
</IfModule>

仅当虚拟主机允许时, 此.htaccess才会重写规则, 因此, 作为最后一步, 我们需要使用以下结构创建虚拟主机。继续编辑虚拟主机文件(xampp \ apache \ conf \ extra \ httpd-vhosts.conf), 并使用以下结构注册你的虚拟主机：

<VirtualHost 127.0.0.1:80>
    DocumentRoot "C:/xampp72/htdocs/php/sandbox/public"
    DirectoryIndex index.php

    <Directory "C:/xampp72/htdocs/php/sandbox/public">
        AllowOverride All
        Order Allow, Deny
        Allow from All
    </Directory>
</VirtualHost>

将更改保存到虚拟主机文件, 然后使用控制面板重新启动apache！

B.没有.htaccess

如官方文档中所述, 如果你选择不使用.htaccess文件, 则将稍微提高Web服务器的性能。但是, 所有与apache相关的配置都必须在虚拟主机文件中完成, 并且默认配置会更改：

<VirtualHost 127.0.0.1:80>
    DocumentRoot "C:/xampp72/htdocs/php/sandbox/public"
    DirectoryIndex index.php

    <Directory "C:/xampp72/htdocs/php/sandbox/public">
        AllowOverride None
        Order Allow, Deny
        Allow from All

        FallbackResource /index.php
    </Directory>
</VirtualHost>

使用AllowOverride将使没有任何.htaccess文件可以覆盖apache指令, 并且在将更改保存到xampp \ apache \ conf \ extra \ httpd-vhosts.conf文件中并重新启动服务器后, 你的项目将立即运行。

设置愉快！