时间戳

首页 > 解决方案 > Symfony 4，在 dev 模式下访问 public/index.php OK，在 prod 模式下访问 KO (404)

symfony - Symfony 4，在 dev 模式下访问 public/index.php OK，在 prod 模式下访问 KO (404)

问题描述

在开发模式下，我使用 apache 服务器，我通过localhost/myApp/public/index.php. 我想用我的 symfony 4 应用程序测试 prod mod。

但是现在，当我打开浏览器并转到 时localhost/myApp/public/index.php，我得到一个 symfony 404 错误页面：

在此处输入图像描述

apache configuratin 看起来不错（我可以在开发模式下毫无问题地访问该网站，并且我得到一个 404 not found 由 symfony 构建，index.php 是由 apache 找到的）。我不明白问题可能出在哪里：/

编辑：下面是 .htaccess 文件的内容（在公共目录中）。我不修改它，这是 symfony 默认的 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>

foo.php编辑3：我在公共目录中创建了php文件<?php echo 'foo';?>，我可以通过我的浏览器毫无问题地访问这个文件。symfony 出了点问题，但无法找到我的错误在哪里......

感谢您的任何帮助 ！

标签： symfonysymfony4production-environment

解决方案

我太傻了。在开发模式下，主页（'/'）不会显示 404，而是 symfony 自动生成的页面。

为什么我在 prod 模式下有 404 的原因是我没有创建一个带有路径“/”的路由的控制器。

因此，prod env 主页中的这个 404 是合乎逻辑的

推荐阅读