Timeline for How do I get my site verified such that it shows a green box in Chrome's address bar?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2016 at 20:57 | history | edited | unknownprotocol | CC BY-SA 3.0 |
word flow
|
| Sep 26, 2016 at 20:55 | comment | added | user | It's perfectly possible to use Stack Exchange almost exclusively over HTTPS, currently excepting site-specific Meta sites and excepting images inlined in posts by users explicitly over HTTP. And the process of getting a DV SSL cert is certainly not laborious, not even before Let's Encrypt. EV certs are another matter, but for a lot of sites, EV certs don't add significant value; HTTPS as opposed to plain-text HTTP does. | |
| Sep 26, 2016 at 20:54 | history | edited | unknownprotocol | CC BY-SA 3.0 |
clarified benefits if https on static-only sites
|
| Sep 26, 2016 at 20:50 | comment | added | unknownprotocol | @MichaelKjörling I know it's always better to serve HTTPS, but for some plain info-only html sites, I think sometimes the process of getting a CA-issues certificate is more hassle than it's worth. | |
| Sep 26, 2016 at 20:45 | comment | added | unknownprotocol | @dhaupin Thanks. The upcoming "Not Secure" warning is news to me, I'll have to read up on that. But even sites that use SSL certs don't encrypt all their traffic (static content)... heck this site doesn't serve everything using https. | |
| Sep 26, 2016 at 20:29 | comment | added | dhaupin | "Often, static websites that aren't very complex, or don't store passwords, or sensitive info don't really need to encrypt their traffic using HTTPS and SSL certificates." If you aren't encrypting every shred of data that hits your server and back to me, I don't really need to be giving you my traffic. Also, any kind of website will take a hit in search rankings if they don't use full HTTPS everywhere. Also also, there is a new address bar icon coming in Chrome that says "Not Secure" in bright red with a warning triangle if the domain is not running HTTPS. ---> i.imgur.com/ahR6dMg.png | |
| Sep 26, 2016 at 12:49 | comment | added | user | "Often, static websites that aren't very complex, or don't store passwords, or sensitive info don't really need to encrypt their traffic using HTTPS and SSL certificates." People disagree. Also note that HTTP/2 isn't supported by any of the major browsers in unencrypted mode, so if you want HTTP/2, you have to talk HTTPS. | |
| Sep 26, 2016 at 10:29 | history | answered | unknownprotocol | CC BY-SA 3.0 |
