I noticed that some of the OAuth pages use insecure content (http:// content on an https:// page):

Okay, so I didn't use freehand circles - so what?

I'm not sure how easy this is to fix but it could potentially scare off some users who don't understand what's going on. Is it possible to have the static content retrieved over https://?

  • This is being worked on, the dialogs (client side flow) should be HTTPS-pure. Everything else will be following soon-ish (CDN is a tad tricky). Commented Dec 7, 2011 at 20:42
  • This is completed-ish. Still trying to find a good solution for application images; everything else on the page should be over HTTPS. I'll post an answer when we've figured that last bit out. Commented Dec 8, 2011 at 1:15


You must log in to answer this question.

Browse other questions tagged .