I just updated to v7.5.13 via nuget, and it looks like the back-end doesn't work if you have umbracoUseSSL = true and you are not browsing using https.
I do not recall this happening in 7.5.10, 7.5.11, nor 7.5.12.
Any ideas of how to fix this so umbracoUseSSL = true can remain enabled?
This is not a bug, this is intended behavior. :-)
umbracoUseSSL is used to mark cookies as secure so obviously they won't work on an insecure connection.
If you need umbracoUseSSL to be true while deploying to your server then you should consider writing a config transform.
I must've removed something in my .config during the update because I never experienced this before in my local environment (perhaps I had a https redirection).
Possible Bug - Back-end breaks in updated 7.5.13
I just updated to v7.5.13 via nuget, and it looks like the back-end doesn't work if you have umbracoUseSSL = true and you are not browsing using https.
I do not recall this happening in 7.5.10, 7.5.11, nor 7.5.12.
Any ideas of how to fix this so umbracoUseSSL = true can remain enabled?
This is not a bug, this is intended behavior. :-)
umbracoUseSSL
is used to mark cookies assecure
so obviously they won't work on an insecure connection.If you need
umbracoUseSSL
to be true while deploying to your server then you should consider writing a config transform.For example, on Umbraco Cloud you can add per-environment transforms: https://our.umbraco.org/documentation/Umbraco-Cloud/Set-Up/Config-Transforms/
The transform would look like this:
Thanks for the reply Sebastiaan.
I must've removed something in my .config during the update because I never experienced this before in my local environment (perhaps I had a https redirection).
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion