Symfony слишком много перенаправлений на apache сервер

Question

Несмотря на то, что я искал в Интернете, я еще не нашел ответа.

Я сделал простой Symfony проект, работающий нормально на dev ENV с Symfony сервером.

Я решил поместить его на apache сервер, чтобы просмотреть его перед некоторым тестом в реальном времени, но у меня возникли некоторые проблемы.

Я сделал часть блога, которая хорошо отображается без поста в нем, но если я добавлю один (или более) сообщение У меня есть ошибка на слишком много перенаправлений. Инструмент разработчика говорит, что у меня много таких запросов: - блог - блог / - блог - блог / - ... и вылетает.

Я использовал пакет symfony / apache, который дал мне .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}::$0 ^(/.+)/(.*)::\2$
    RewriteRule .* - [E=BASE:%1]

    # Sets the HTTP_AUTHORIZATION header removed by Apache
    RewriteCond %{HTTP:Authorization} .+
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%0]

    # 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.
    # Rewrite all other queries to the front controller.
    RewriteCond %{REQUEST_FILENAME} !-f
    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>

Я использую конфигурацию сайта apache:

<IfModule mod_ssl.c>
<VirtualHost *:443>
    ServerName mydomain
    ServerAlias www.mydomain

    # Uncomment the following line to force Apache to pass the Authorization
    # header to PHP: required for "basic_auth" under PHP-FPM and FastCGI
    #
    # SetEnvIfNoCase ^Authorization$ "(.+)" HTTP_AUTHORIZATION=$1

    # For Apache 2.4.9 or higher
    # Using SetHandler avoids issues with using ProxyPassMatch in combination
    # with mod_rewrite or mod_autoindex
    #<FilesMatch \.php$>
        #SetHandler proxy:fcgi://127.0.0.1:9000
        # for Unix sockets, Apache 2.4.10 or higher
        # SetHandler proxy:unix:/path/to/fpm.sock|fcgi://dummy
    #</FilesMatch>

    # If you use Apache version below 2.4.9 you must consider update or use this instead
    # ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9000/var/www/project/public/$1

    # If you run your Symfony application on a subpath of your document root, the
    # regular expression must be changed accordingly:
    # ProxyPassMatch ^/path-to-app/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9000/var/www/project/public/$1

    DocumentRoot "/var/www/html/public"
    <Directory "/var/www/html/public">
        # enable the .htaccess rewrites
        AllowOverride All
        Require all granted
    </Directory>

    # uncomment the following lines if you install assets as symlinks
    # or run into problems when compiling LESS/Sass/CoffeeScript assets
    # <Directory /var/www/project>
    #     Options FollowSymlinks
    # </Directory>

    ErrorLog /var/log/apache2/project_error.log
    CustomLog /var/log/apache2/project_access.log combined

Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile 
SSLCertificateKeyFile 
</VirtualHost>
</IfModule>

(некоторые части были изменены / удалены, например, путь или имя домена)

Мой контроллер блога выглядит так:

 /**
     * @Route("/blog/articles", name="blog")
     */
    public function index()
    {
        $blogpost = $this->getDoctrine()
            ->getRepository(BlogPost::class)
            ->findAll();

        if (!$blogpost) {
            $nopblogost = true;
        } else {
            $nopblogost = false;
        }
        return $this->render('blog/index.html.twig', [
            'controller_name' => 'BlogController',
            'page_title' => "mon Blog",
            'message' => null,
            'page_class' => "path-blogpage",
            'blog_empty' => $nopblogost,
            'blogpost' => $blogpost
        ]);
    }

    /**
     * @Route("/blog/post/{id}", name="blogpost")
     */
    public function view($id)
    {
        $blogpost = $this->getDoctrine()
            ->getRepository(BlogPost::class)
            ->find($id);

        if (!$blogpost) {
            $nopblogost = true;
        } else {
            $nopblogost = false;
        }
        return $this->render('blog/view/index.html.twig', [
            'controller_name' => 'BlogController',
            'page_title' => $blogpost->getTitre(),
            'message' => null,
            'page_class' => "path-blogpage",
            'blog_empty' => $nopblogost,
            'post' => $blogpost
        ]);
    }

Странный факт: когда я в качестве примера изменяю маршрут на «блог / список», он работает нормально. Вернуться к ошибке «блог» снова.

Я не понимаю, некоторые ли страницы c перенаправляются как «главные», а подстраница «main / sub» обрабатывается как блог, но без взаимодействия с базой данных.

У кого-нибудь возникла проблема?