Issue Bug Closed

#106117baseVariant base on applicationContext Development not used for absolute URI

Holger Drosdek 02/07/25, 15:23 updated 02/10/25, 16:43

Description

When having base: / in config.yaml and an additional baseVariant base: ‘https://dev.example.com’ on condition: ‘applicationContext == “Development”’ no absolute URI can be build, e.g. by fluid Uri.action.
Only when main base has been edited with DEV-Domain like this

base: 'https://dev.example.com'
baseVariants:
  -
    base: 'https://dev.example.com'
    condition: 'applicationContext == "Development"'

the absolute URI is being build e.g. by fluid Uri.action.

Application Context setting has been established via .htaccess

    # Rules to set ApplicationContext based on hostname
    RewriteCond %{HTTP_HOST} ^dev\.example\.com/$
    RewriteRule .? - [E=TYPO3_CONTEXT:Development]
    RewriteCond %{HTTP_HOST} ^www\.example\.com$
    RewriteRule .? - [E=TYPO3_CONTEXT:Production]

This seems to be intended, as the description of entry point tells me
“Wenn es nur ein / ist, können Sie sich nicht darauf verlassen, dass TYPO3 die vollen URLs erzeugt.“
(If it’s just a /, you can’t rely on TYPO3 to generate the full URLs.)

This has been different in Typo3 11.5 and I’m wondering, for which purpose the baseVariants actualy are.

Reviews 0

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