Recently a site of ours has started using HTTPS for all traffic (URL rewrite rule in web.config). Since that time the preview of a Courier form in the richttexteditor is not displaying anymore and takes a long time to load (about 30 seconds). When i remove the rewrite for forcing HTTPS the form is displayed in the richtexteditor instantly so it seems like a HTTPS issue with Contour.
I'm running Umbraco 4.11.10 with Contour 3.0.1. Is there some setting in Contour which can resolve this?
For now i fixed it by forcing all Umbraco traffic back to using HTTP instead of HTTPS. If anyone has any idea's how to solve the underlying issue that would be appreciated.
Have you tried running it in Chrome and looking at the Developer Tools window to see if there were any errors detected?
Usually when I run across an issue with content not loading in https it is because the content is being called over http instead and the browser is blocking it.
Not sure if this will be helpful, but you could check this line in the web.config file and see if it is set to true:
Displaying form in WYSIWYG when using HTTPS
Recently a site of ours has started using HTTPS for all traffic (URL rewrite rule in web.config). Since that time the preview of a Courier form in the richttexteditor is not displaying anymore and takes a long time to load (about 30 seconds). When i remove the rewrite for forcing HTTPS the form is displayed in the richtexteditor instantly so it seems like a HTTPS issue with Contour.
I'm running Umbraco 4.11.10 with Contour 3.0.1. Is there some setting in Contour which can resolve this?
For now i fixed it by forcing all Umbraco traffic back to using HTTP instead of HTTPS. If anyone has any idea's how to solve the underlying issue that would be appreciated.
Have you tried running it in Chrome and looking at the Developer Tools window to see if there were any errors detected?
Usually when I run across an issue with content not loading in https it is because the content is being called over http instead and the browser is blocking it.
Not sure if this will be helpful, but you could check this line in the web.config file and see if it is set to true:
is working on a reply...