Message of the day:
Welcome to SilverStripe | Current stable: https://goo.gl/C4F1T9 | Feature requests: https://goo.gl/EcQ34L | Community Forum: https://forum.silverstripe.org | StripeCon EU 2019! https://stripecon.eu
If you have any SilverStripe related questions, please supply the version of Framework you're using.
Did you flush? 🚽 =
There is a mixed-content message though 🙂
I was hoping to find an analytics script that wasn’t opt-in, for maximum irony 😞
If I weren't busy that day, obviously
I'd pay good money to go to that
But frankly, I don't know why
It's free to attend
Cheers for chipping in @brett.tasker what you said was exactly why the 301 redirect was occurring.
forceSSL() trigger after
!isDev check in the
_config.php file. It's not using a proxy to terminate but instead NGINX serves the site but that sits behind some other things like Ambassador that take care of the ssl stuff so NGINX shouldn't be concerned with it.
You may find this still has the same issue. As "Ambassador" is terminating the SSL, Nginx only sees connections come on port 80 and assumes it is http:// request.
You may find that Ambassador sends custom headers to identify when the connection is SSL or not. These headers can be used within Silverstripe CMS to tell Silverstripe if the connection is over HTTPS or not.