UmbracoApplicationUrl acts as the fallback base URL when Umbraco cannot determine a hostname from the content tree.
This typically happens when:
- No hostname has been assigned to the root content node.
- You're using hostless root paths such as:
//en/pl
In these scenarios, Umbraco uses UmbracoApplicationUrl as the base for generating absolute URLs, redirects, and other routing decisions.
If you instead configure a hostname on the root content node (via Culture and Hostnames), that hostname takes precedence over UmbracoApplicationUrl.
For example, if your site has a hostname configured as:
https://cd1.dev.localhost
or, for language variants:
https://cd1.dev.localhost/en
https://cd1.dev.localhost/pl
then Umbraco uses those hostnames for request routing and URL generation. In that case, UmbracoApplicationUrl is only used as a fallback if no matching hostname can be resolved.
This allows a multi-site or multilingual setup to generate the correct URLs for each site and culture while still providing a sensible default for hostless configurations.