Google has announced that HTTPS will be used as a lightweight ranking signal for search results; sites that use it will appear slightly higher (although they make clear that quality content is a higher signal).
This discussion has been archived.
No new comments can be posted.
That's what DPI is for. Self-sign a certificate and exclude anything you don't want inspected (like your bank). It cuts down on the viruses trying to bypass proxy a/v checks too!
Not at all. The same machine can be running an http server on port 80 as is running an https server on port 443.
If load's what you're worried about getting to be too much (as https does have put a bit more load on a server, though not as crazy as some have made it out to be), it's worth remembering that you can have 10 servers all sitting behind the same public IP if you're so inclined, with methods in place to handle load balancing.
The same machine can be running an http server on port 80 as is running an https server on port 443.
I don't think that's what the poster was referring to. Before the SNI extension to SSL was widespread, you had to have a separate IP address for each HTTPS site.
(Score: 3, Interesting) by cafebabe on Friday August 08 2014, @08:11PM
Does this move create extra pressure on IPv4 space?
1702845791×2
(Score: 0) by Anonymous Coward on Friday August 08 2014, @08:43PM
No
But it does create pressure on my squid cache that I use for lowering my bw to the outside world and the upcoming caps my ISP wants to put in place.
(Score: 1) by datapharmer on Friday August 08 2014, @09:13PM
That's what DPI is for. Self-sign a certificate and exclude anything you don't want inspected (like your bank). It cuts down on the viruses trying to bypass proxy a/v checks too!
(Score: 0) by Anonymous Coward on Saturday August 09 2014, @01:15AM
Didnt really want to MITM attack myself. Been meaning to do exactly what you said for awhile though. Just a PITA.
(Score: 2) by cykros on Friday August 08 2014, @11:56PM
Not at all. The same machine can be running an http server on port 80 as is running an https server on port 443.
If load's what you're worried about getting to be too much (as https does have put a bit more load on a server, though not as crazy as some have made it out to be), it's worth remembering that you can have 10 servers all sitting behind the same public IP if you're so inclined, with methods in place to handle load balancing.
(Score: 1) by Mr. Slippery on Saturday August 09 2014, @05:29AM
I don't think that's what the poster was referring to. Before the SNI extension to SSL was widespread, you had to have a separate IP address for each HTTPS site.