Viewing 7 replies - 1 through 7 (of 7 total)
  • LindzConnell

    (@lindzconnell)

    Hello Jason,

    We are not yet compatible with SSL. We’ll most likely be addressing this sometime this year, however, we do not currently have an ETA.

    Check back with us anytime, though.

    Thank you!

    Lindz
    Diverse Solutions

    Thread Starter jasonthoele

    (@jasonthoele)

    Thanks for the heads up, I hope this is a priority with your development team that will be done more sooner than later. With Google putting an emphasis on ranking now for sites with SSL it’s not just a convenience its a requirement.

    As an interim work around, would you consider adding a SSL certificate to your static resource CDN? If that was implemented then a site with a front end proxy or post processor could update the CDN URLs to be SSL.

    Hello Ron,

    Unfortunately, not at this time. As we have more information, though, we’ll be sure to update our customers.

    rstimmler

    (@rstimmler)

    It is now almost a year later and this still has not been addressed. Chrome has implemented their first non-https warning in their browsers. Please advise.

    LindzConnell

    (@lindzconnell)

    Hello Rstimmler,

    We are hoping to have a resolution for this in the near future. There is no current ETA at this time but we are working towards a solution.

    Thank you,

    Lindz

    @wpmuguru – Looks like https://cdn1.diverse-cdn.com/ is setup for HTTPS. Maybe relative protocols for CDN urls could help now.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘SSL Compatibility’ is closed to new replies.