Can you use a different domain for other languages?

[MajPay]

In Typo3 you can have the default language open with Domain foo.com but the translation open with Domain bar.com. How Can i achieve the same for the headless / frontend?

What we want:

typo3.foo.com => typo3 json api
foo.com => frontend

typo3.bar.com => typo3 json api for translation
bar.com => frontend for translation

[lukaszuznanski]

@MajPay You can have the same setup like in standard TYPO3, so yes, that's possible.

[MajPay]

This is totally buggy i think, at least we can't manage to configure this. In some parts there will alway be the frontend-base mixed with the path of the backend path.

[MajPay]

UrlUtility::getFrontendUrlWithSite will always override the language specific settings, that may have been set by the request handling. The additional frontend-path is only prefixed, if the generated $url contains the hostname of the site-base. This won't work because the url is most likely not absolute and does not contain any host. A potentially existing extra-path in the site-base is never taken into account when generating the frontend uri.

I think the UrlUtility is too bugy for production use

[tmotyl]

@MajPay we use this kind of configuration for some proejcts.
Please provide more context how to reproduce the issue.

[MajPay]

Well we have a "multisite" setup and this customer wants each language version for each site to be available with a separate root domain. So the frontendBase has to be configured in the siteLanguage. For the live environment we ended up with separate domains for each site / language for the backend api as well. By having the base path the same for the frontend and json api we managed to work around the issue. In local development and staging environment i wanted to achieve a single domain for the backend-api and separate domains for each frontend version.

But we have issues everywhere:

Links will always be composed like {frontendBase}/{backendPath}/{slug}
Cross-Language-Links (Language menu) has issues
The canonical has issues

At the moment i try to replace the UrlUtility to overcome those issues. It's pretty easy to fix most parts but the Language-Menu and Canonical Generation remain buggy.

[MajPay]

The HeadlessHreflangGeneratorListener does not take the language configuration into account. That part needs to be replaced as well

[MajPay]

And the links generated under i18n are also wrong

My pattern to deal with those situations was to make sure to call withRequest before and setting the language attribute for the request to the correct language. In the UrlUtility (my own implementation) i won't call the handleSiteConfiguration in getFrontendUrlWithSite method to avoid losing the language config.

Now all URLs are correct no matter how they are configured.

[tmotyl]

@MajPay please provide steps to reproduce the issue on fresh TYPO3 with Headless. Including details like ts configuration, TYPO3 and headless versions etc.