I’m currently working with an APEX application that uses "friendly URLs". However, I’ve noticed that when APEX generates links for theme resources such as CSS and icons, it does not use the application alias—instead, it references the application ID.
<link rel="stylesheet" href="[r/shq\_public/**600000**/files/theme/142/v77/58319491267142685.css](https://ordsdev.nuage-externe.habitation.gouv.qc.ca/fg/r/shq_public/600000/files/theme/142/v77/58319491267142685.css)" type="text/css" />
<link rel="stylesheet" href="[r/shq\_public/files/static/v845/css/shq.min.css?v=release%201.0](https://ordsdev.nuage-externe.habitation.gouv.qc.ca/fg/r/shq_public/files/static/v845/css/shq.min.css?v=release%201.0)" type="text/css" />
<style nonce="Rg0pkz5X0xjr1upYSKRkrg" >.shq-lien-not-allowed a { cursor:not-allowed; }
</style>
<link rel="apple-touch-icon" href="[r/shq\_public/**600000**/files/static/v16/icons/app-icon-192.png](https://ordsdev.nuage-externe.habitation.gouv.qc.ca/fg/r/shq_public/600000/files/static/v16/icons/app-icon-192.png)" /><link rel="icon" href="[r/shq\_public/**600000**/files/static/v16/icons/app-icon-32.png](https://ordsdev.nuage-externe.habitation.gouv.qc.ca/fg/r/shq_public/600000/files/static/v16/icons/app-icon-32.png)" />
This behavior is causing complications with the configuration of our public load balancer. Specifically, we are required to duplicate routing rules: one set for the application alias and another for the application ID. This adds unnecessary complexity and increases the risk of misconfiguration.
Would it be possible to configure APEX so that these resource links consistently use the alias, in line with the friendly URL format?