Bug #93368
open
Domain redirects to records not working anymore
0%
Description
Given domain redirects to records when a domain for such a redirect is requested a 404 error is triggered instead of a redirect.
Criteria to trigger this behavior:
- The
baseof all sites must be a full URL likehttp://example.org/, not simply/(slash). - The incoming domain must not be the
baseof any site. - The redirect must point to a record URN like
t3://record?identifier=<identifier>&uid=<uid>. (There's an automatic fallback in case oft3://pageURNs.)
The incoming domain does not match the base of any site which is why a NullSite is used instead while matching redirects. Due to this TypoScriptFrontendController::getPageAndRootline() (called from RedirectService::bootFrontendController()) triggers an immediate 404 response. This prevents the record URN to be resolved to a valid URL.
As a workaround one can override RedirectService::getTargetUrl() and fall back to any valid site.
Updated by Mathias Brodala almost 4 years ago
- Subject changed from Domain redirects not working anymore to Domain redirects to records not working anymore
Updated by Oliver Hader about 2 years ago
- Sprint Focus set to On Location Sprint
Updated by Susanne Moog about 2 years ago
I'm a little confused as to how this is supposed to work. The record link handler could belong to multiple sites (with multiple different target page ids) - how should the correct redirect target be determined? As far as I understand, this will not work with the record link handler, and would require a page id set (and therefor a custom link handler that supports it).
Updated by Benni Mack over 1 year ago
- Status changed from New to Needs Feedback
Question is still valid
Updated by Mathias Brodala 9 months ago
One would need to resolve the record URL at least until the link parameter is known. Then the site could be looked up.
However, one may need a site, its related root page and the related TypoScript setup to resolve said parameter.
I fear this is a chicken-egg problem which cannot be resolved easily.
Updated by Benni Mack 9 months ago
We might be able to fix this behaviour in v13 with the resolving of TypoScript and TSFE