Yes. Our scripts automatically detect whether content should served as HTTP or securely with HTTPS. If you are experiencing issues behind HTTPS where content is not appearing or you are receiving secured content errors, this means you are using an outdated script or are hard-coding the script's protocol. Write urls as "//ws.cnetcontent.com" instead of "http://ws.cnetcontent.com"
- Bare Inline Content on HTTPS: https://cc.cnetcontent.com/contentcast/perf_tests/basic_1.html
- Inline Content on a HTTPS page: https://usm.channelonline.com/acme/ccs/Products/index.co?id=M009530761
- HTTPS Showcase Example: https://cc.cnetcontent.com/vcs/lenovo/showcase.html