#101505Domain with non-ascii symbols causes a 503 for "page not found" handling
Description
Page not found handling is broken for domains with non-ascii names:
1. You have a domain name like áéćž.com
2. You have the following error handling configuration:
errorHandling:
- errorCode: 404
errorHandler: Page
errorContentSource: 't3://page?uid=6'
The result for non-existing pages is:
503 Page Not Found External error page could not be retrieved. Client error: `GET https://áéćž.com/404/` resulted in a `401 Unauthorized` response: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title>Seite nicht gefunden</title> <meta nam (truncated...)
The problem is in EXT:core/Classes/Error/PageErrorHandler/PageContentErrorHandler.php, near line 103:
$this->pageUid = $urlParams['pageuid'] = (int)($urlParams['pageuid'] ?? 0);
$resolvedUrl = $this->resolveUrl($request, $urlParams);
The urls needs to be converted to punycode before passing it to the request. It should fetch https://xn--1caq4gov.com/404/ instead of https://áéćž.com/404/.
We use squid proxy for non-local sites. Not sure if it is important.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 3
-
Dmitry Dulepov changed subject
Domain with non-ascii symboles causes a 503 for "page not found" handlingDomain with non-ascii symbols causes a 503 for "page not found" handling <span data-processor="relativetime" data-value="2023-07-31T11:37:48+00:00" > 07/31/23, 11:37 </span> -
Dmitry Dulepov commented <span data-processor="relativetime" data-value="2023-07-31T11:40:39+00:00" > 07/31/23, 11:40 </span>
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2025-04-23T19:42:05+00:00" > 04/23/25, 19:42 </span>can’t reproduce that on v14 (and v13 should behave the same), as this has been fixed with #98396 and followup issues.
\TYPO3\CMS\Linkvalidator\Linktype\ExternalLinktype::preprocessUrl()does it correctly.