Insecure Content Warnings (HTTPS)

Nathan Rajlich

unread,

Jun 21, 2011, 8:00:03 PM6/21/11

to disqu...@googlegroups.com

Hey guys, thanks for your hard work getting HTTPS supported!! Everything is working great. The only (minor) problem I'm experiencing is with the "default" avatar for user comments. It's currently being served from "http://mediacdn.disqus.com/1308681305/images/noavatar32.png", which causes a warning like:

2The page at https://tootallnate.net/nodejs-on-ios displayed insecure content from http://mediacdn.disqus.com/1308681305/images/noavatar32.png.

Hoping this can be worked out shortly. Thanks in advance!

Nathan Rajlich

unread,

Jul 6, 2011, 11:17:37 PM7/6/11

to disqu...@googlegroups.com

dude... seriously?

Ryan Witt

unread,

Jul 6, 2011, 11:34:20 PM7/6/11

to Disqus Developers

+1

maybe it's a certificate rollout problem

On Jul 6, 11:17 pm, Nathan Rajlich <nat...@tootallnate.net> wrote:
> dude... seriously?
>
> On Tue, Jun 21, 2011 at 5:00 PM, Nathan Rajlich <nat...@tootallnate.net>wrote:
>
>
>
> > Hey guys, thanks for your hard work getting HTTPS supported!! Everything is
> > working great. The only (minor) problem I'm experiencing is with the

> > "default" avatar for user comments. It's currently being served from "*
> >http://mediacdn.disqus.com/1308681305/images/noavatar32.png*", which

> > causes a warning like:
>
> > 2The page athttps://tootallnate.net/nodejs-on-iosdisplayed insecure

> > content fromhttp://mediacdn.disqus.com/1308681305/images/noavatar32.png.