Proper TLS certificate on missing


It is great to see that almost all ressources of AMR can be rewritten to use TLS.
Only the pictures on can’t because the certificate is not valid for the domain.


Not sure why you are getting that… I just checked and the certificate is still valid. Otherwise you would get all sorts of warnings on e.g. the account pages served over https.

#3 works, but it causes mixed content warnings because pictures like are transferred inscurely.

This site only has a valid cert for

 *, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *,,,,,,,,,,,,,,,, *, *,,,,, *, *,,,,, *,,,,,,, *,,,,, *, *,,,,, *,,,,,,, *, *, *, *, *,, *, *, *,,,,,,, *, * 

not for

Securing only the login page won’t help much against determined people trying to get your credentials because the rest of the page can still be modified on the wire.


From the Gear Optimized page.


If you are manually switching to https, you would need to change the css to use image urls that are https also. We do this automatically on our pages designed to work over https, we have separate stylesheets for them.

Also, we have two different certificates, one for the “www” subdomain, and one for all the other subdomains.


I don’t. I just go to and this warning pops up at chrome console.


Yeah the home page should just be http, not https. It isn’t designed to run as an https page right now.


OK – I think I see what’s up, there is a javascript somewhere that generates an icon URL, and it is hard-coded to the non-https version at the moment. I can see if I can change that, should get rid of the mixed content message for people who want to use https instead of the normal http.

@espenlaub Just to reiterate, we have an ssl certificate for the static (and static2) subdomain, but it is a different certificate than the one for our main site. I’ll check… it could be that those couple icons are coming from a different CDN that doesn’t have the certificate. Regardless, it’s just a couple icons.

Also, there is a second level of authentication required to access any account-related page. The login information that gives you access to the non-https pages is not sufficient by itself to grant access to an account page.