19 Jan 2011
24 May 2012
Link to this post
We had a Sitefinity 4.3 site, fully in HTTPS, which worked properly. After the update to Sitefinity 5.0 (SP1), we're getting critical problems related to content URLs. In the site administration settings, under System / Site URL Settings, we checked the "Enable non-default Site URL Settings", and set the site host (without the leading protocol, example: "mysite.com"). Result: content likes images are served through http, not https, which naturally causes warnings. These images should be served as https, and we don't understand why they aren't. Is this a Sitefinity bug?
With Sitefinity 4.3, we actually had the protocol in front of the host, which worked and was apparently supported. But this no longer works with Sitefinity 5.0, which doesn't expect the protocol to be here.
We tried setting the http and https protocol ports, but this didn't help.
Thanks for your help.