Hi RobertT,
I've been advocating for a workaround for this with Engineering. They asked if you tried switching the browser to allow mixed content. I couldn't tell from your post.
This is becoming a bigger issue for us now, Apple have removed the option from Safari 11 to enable mixed/insecure content so this is no longer a viable workaround.
Do we know if the SDK will be updated to allow us to serve-sass over a HTTPS service?
Just an update for anyone following this topic.
I've managed to workaround the issue by setting up an SSL server in apache with symlinks to the assets folders in the SDK - not elegant I know but it means that my machine serves up the SDK via HTTPS - the caveat is that it's not a straightforward process to achieve and I've only been able to do this on a Mac so far.
If I figure a more robust way of running a HTTPS server with simpler setup on different machines I'll share my findings.
