Issue Bug Closed

#99091cURL-exception with umlaut-domains on requests for sitemaps

Thomas Sam Wittich 11/15/22, 10:29 updated 04/08/25, 12:55

Description

Dear typo3-team,

with a site with a umlaut-domian i get following exception in the /typo3/var/log/typo3_*.log

ue, 15 Nov 2022 11:16:37 +0100 [CRITICAL] request=“9c6573d6f9fda” component=“TYPO3.CMS.Core.Error.ProductionExceptionHandler”: Core:
Exception handler (WEB: BE): GuzzleHttp\Exception\RequestException, code #0, file /html/typo3/vendor/guzzlehttp/guzzle/src/Handler/Cur
lFactory.php, line 211: cURL error 3: (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) – {mode“WEB”,application_mode“BE
”,exception_class“GuzzleHttp\\Exception\\RequestException”,“exception_code”:0,“file”:”/html/typo3/vendor/guzzlehttp/guzzle/src/Hand
ler/CurlFactory.php”,“line”:211,“message”:“cURL error 3: (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)”,request_url“htt
ps://www.xn—freie-whler-schorndorf-64b.de/sitemap.xml”,exception

The mentioned url with the already transformed domain-name for the curl call is:
https://www.xn—freie-whler-schorndorf-64b.de/sitemap.xml
The original url before the transformation is not mentioned in the exception, but so it is:
https://www.freie-wähler-schorndorf.de/sitemap.xml

That means:
cURL is getting an error 3; according to https://curl.se/libcurl/c/libcurl-errors.html this error means:

CURLE_URL_MALFORMAT (3)
The URL was not properly formatted.

But, the site with the umlaut-domnain otherwise is correct. All pages are reachable in all browsers. Just for the sitemap Typo3 does an internal call with cURL via guzzle, this one then fails for an unkown reason.

The error does only appear on [some?] umlaut-domains.

Any ideas?

Reviews 0

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

History 1

  1. Benni Mack commented and changed status New Closed 04/08/25, 12:55

    Hey thomas.

    we’ve fixed this (in v11 there is a a feature flag “subrequestPageErrors”) which should solve your problem by NOT having a cURL call anymore. In v12 this option is enabled by default. I think you don’t have that problem anymore, since your website is now running v13 LTS. Thanks for your report anyways.

    I will close your issue, if you feel this is still wrong, let me know and I can re-open the issue with more details in current versions.

    All the best,
    Benni.