I’m currently trying out a few of your services, one of which is your HTTP > HTTPS service and I have an odd issue.
A number of files are triggering a Mixed content message and is therefore blocked from running.
After much digging I have discovered case of the filename nad path are at fault.
As an example, I have a stylesheet that is blocked because of a mixed content message in Chrome and Firefox (not IE). The href path in the page is /StyleSheets/Default.css. The filename and directory on the file system are named the same way \StyleSheets\Default.css.
I’ve found that if I change the href path to be all lowercase: /stylesheets/default.css hey presto it works!
However, that is one of many files with mixed case lettering some of which are generated as bundles with random names/cases which I have little to no control over.
Does anyone know of a way to fix this or why is might be happening?