4 ms·
> Kind of. HTTP was designed with caching in mind, so the idea was that if you GET a page it should more or less not change and you could add headers and stuff
by johnmaguire2013 6y ago
> Kind of. HTTP was designed with caching in mind, so the idea was that if you GET a page it should more or less not change and you could add headers and stuff to instruct proxy servers about whether to cache or not and for how long. I think you could use HEAD then to check if a page had changed ...
Nothing in the HTTP spec has changed about this AFAIK. The internet still behaves this way.
> Anyway, you can no longer take this approach because bad people broke the Internet and now you have to have a great honking opaque TLS layer between you and the caching servers so there's no way for this optimisation to work any more.
You could certainly still do this, you just need to import the proxy's CA certificate into your browser. It's just not possible to do to others on your network without consent now. (This is a security feature, not a bug.)
- rusk 6y agoI’m all ears ... got any pointers for me? I was under the impression that TLS everywhere breaks the web as it was designed, ergo though nothing in the spec has changed - the environment itself has changed. You could probably do something with isomorphic encryption but nobody seems that bothered. It’s probably of limited value nowadays as we use the web more as an rpc layer.
- hnick 6y agoIt's what bigcorps do to monitor employee traffic, my work laptop has a certificate installed so they can snoop and proxy traffic. Setup will vary by proxy and OS but here's one example (which I haven't used but at a glance seems OK): https://www.ssltrust.com.au/help/setup-guides/setup-squid-proxy https://www.ssltrust.com.au/help/setup-guides/setup-squid-pr...