andygambles

25 ms·

1. 211.▲
   by andygambles 13y ago

   Which makes it even more stupid that they haven't put this as the source code.
2. 212.▲
   by andygambles 13y ago

   So while loading the seal over standard http is not a security issue in itself there is the problem of mixed content when loaded over https. This could leave the site open to a MiTM style attack since security fatigue means the user just lo
3. 213.▲
   Comodo not really getting the concept of HTTPS(servertastic.tumblr.com)

   5 points by andygambles 13y ago|7 comments
4. 214.▲
   by andygambles 13y ago

   With RapidSSL if you order a cert for www.domain.com then it will also cover domain.com. But if you order a cert for domain.com or sub.domain.com then it will NOT secure the www.domain.com. So basically make sure your CSR request is for www
5. 215.▲
   by andygambles 13y ago

   Usually the CDN will have a single certificate which then has multiple SAN entries. What can happen depending on the size of the CDN is it can take a long time for the SSL to be added to the SAN entries on all the edge servers. So if a site
6. 216.▲
   by andygambles 13y ago

   Because www.bing.com is served by akamai CDN which is different to bing.com. Therefore the SSL on the site is different.
7. 217.▲
   A look at the cost of SSL certificates(blog.servertastic.com)

   1 points by andygambles 14y ago|0 comments