had a similar issue when I was setting up a local docker environment that was doing the same thing
@halles maybe look at
SS_TRUSTED_PROXY_IPS here: https://docs.silverstripe.org/en/4/developer_guides/security/secure_coding/#request-hostname-forgery
depending on what you're trying to do you could implement your own TemplateGlobalProvider: https://api.silverstripe.org/4/SilverStripe/View/TemplateGlobalProvider.html
does anyone know if/how
SS_BASE_URL is configured in CWP environments?
any idea how I would reliably find the base URL from something like a queued job in that case? do I just need to implement my own solution to handle that?
or alternatively can we request
SS_BASE_URL is set on a case by case basis?
Probably worth chucking in a helpdesk ticket as it's been a while and I'm not sure what the preferred solution is nowadays, but they can add custom environment variables if required 👍
or where you want to get at the actual db value use
yeah you'll want those ^^^
you should read the link I sent above and set the relevant values in your .env for SS_TRUSTED_PROXY_IPS
you might be getting affected by this: https://docs.silverstripe.org/en/4/developer_guides/security/secure_coding/#request-hostname-forgery
are you serving the site from behind a proxy?
setup a test version of the site and show them that?