[Issue] Fix exception handling inconsistency between developer and production modes

[m2-assistant]

This issue is automatically created based on existing pull request: #37712: Fix exception handling inconsistency between developer and production modes

---

Description (*)

During developing our custom module was found an issue in the developer mode, for example, after implementing \Magento\Customer\Controller\AccountInterface class into the custom controller we got redirected to the login page (as was expected), but on the production on the same flow we got an internal server error 500.
It happened because the redirect URL was set to the response before the trigger exception and as a result Location header was sent to the browser and the browser redirect to the login page instead of the page with an exception message.
It's not expected flow between developer and production modes and can cause some issues for production.

Preconditions and environment

• Magento 2.4.5
• Controller, which sets a redirect and throws an exception

Steps to reproduce

1. Create a module:

app/code/Vendor/Module/registration.php:

<?php

use Magento\Framework\Component\ComponentRegistrar;

ComponentRegistrar::register(ComponentRegistrar::MODULE, 'Vendor_Module', __DIR__);

app/code/Vendor/Module/etc/module.xml:

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:framework:Module/etc/module.xsd">
    <module name="Vendor_Module"/>
</config>

app/code/Vendor/Module/etc/frontend/routes.xml:

<?xml version="1.0" encoding="UTF-8"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:App/etc/routes.xsd">
    <router id="standard">
        <route id="vendor" frontName="vendor">
            <module name="Vendor_Module"/>
        </route>
    </router>
</config>

magento2/app/code/Vendor/Module/Controller/Example/Index.php:

<?php

namespace Vendor\Module\Controller\Example;

use LogicException;
use Magento\Customer\Model\Session;
use Magento\Framework\App\Action\HttpGetActionInterface;
use Magento\Framework\App\ResponseInterface;
use Magento\Framework\Controller\ResultInterface;
use Magento\Framework\Exception\SessionException;

class Index implements HttpGetActionInterface
{
    public function __construct(private readonly Session $customerSession,)
    {
    }

    /**
     * Execute action based on request and return result
     *
     * @return ResultInterface|ResponseInterface
     * @throws LogicException
     * @throws SessionException
     */
    public function execute()
    {
        // Here, you will be redirected to the login page when not logged in.
        $this->customerSession->authenticate();

        throw new LogicException(__('Some exception text'));
    }
}

2. Go to www.domain.com/vendor/example

Expected result

• Page with exception text like this one:

Actual result

• Redirect to the login page

Unfortunately, I don't have enough experience with test coverage, will be great if someone covers this case by test.

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-11829 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Charlie. Thank you for verifying the issue.
Issue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.