Issue Bug Closed

#107548Page error handler with type page can not handle redirects

Thorben Nissen 09/26/25, 12:59 updated 11/05/26, 07:39

Description

The homepage, which at least has `/` as slug, is the error page for 403, as the login form is placed on the homepage. When hitting an access restricted page, the error handling creates and URL that is `my.host/en/`, which is the base URL for the english site language. The site base redirect resolver thinks it must redirect to `my.host/en` which leads to a redirect response, which can not be handled by the page error handler. Instead it throws an exception.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 2

  1. Oliver Bartsch commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-05T07:39:55+00:00" > 11/05/26, 07:39 </span>

    Hey,

    thanks for the report. With a language base of “/en” (no trailing slash), the URL generated for the root page (slug “/”) is “/en/”. SiteBaseRedirectResolver answers that with a 307 to “/en”. PageContentErrorHandler sends its subrequest internally and does not follow redirects, so any status >= 300 ends in RuntimeException 1544172839.

    The underlying problem is exactly what #106757 is about: the error handler subrequest has to handle redirects. I’m closing this one as a duplicate and will continue in #106757.

    Until that is merged, you can set the language base to “/en/” (with trailing slash). Then the generated URL matches the base and no redirect happens.

    Cheers, Oli