4 ms·
> In the era of HTTP, you could have set up a web server in 2000 and it could still be running today, working perfectly well (even if it didn't support the very
by tleb_ 6y ago
> In the era of HTTP, you could have set up a web server in 2000 and it could still be running today, working perfectly well (even if it didn't support the very latest shiny thing).
I'm not sure this assumption is right, looking at the CVE list and in particular entries associated with Apache.
http://cve.mitre.org/cve/ http://cve.mitre.org/cve/
https://www.cvedetails.com/product/66/Apache-Http-Server.html?vendor_id=45 https://www.cvedetails.com/product/66/Apache-Http-Server.htm...
- richardwhiuk 6y agoI agree - it's completely naive to believe that any software deployed 20 years ago, and open to public attack, with zero maintenance wouldn't be attacked, and compromised. I'd like that to be the world we live in - and with the continual evolution in secure programming practices, maybe one day it might be, but it's not. As a profession of software engineers, we have not achieved the level of quality at the costs that is willing to be met to engineer public facing websites that won't be vulnerable to attack at some point in the next 20 years, and will still be running.
- fomine3 6y agoI believe OP want to say that it just not stops working
- l0b0 6y agoI think the GP comment demonstrates that it very likely will stop working very shortly if left on the open web.