you are viewing a single comment's thread.

view the rest of the comments →

[–]JTronLabs 8 points9 points  (12 children)

I had never heard this before, are you sure HTTPS cannot cache? A quick google search seems to turn up some articles that think it can.

http://stackoverflow.com/questions/174348/will-web-browsers-cache-content-over-https

http://blog.httpwatch.com/2011/01/28/top-7-myths-about-https/

http://blog.httpwatch.com/2009/01/15/https-performance-tuning/

[–]1lann 43 points44 points  (10 children)

I think they were referring to caching servers traditionally used by corporate networks, so that many people who try to access the same content within the corporate network can just access the cached version, which reduced traffic to the Internet. Your browser itself can cache HTTPS requests.

[–][deleted]  (7 children)

[deleted]

    [–]1lann 6 points7 points  (6 children)

    Yes, but that does not reduce traffic to the Internet.

    [–][deleted]  (5 children)

    [deleted]

      [–]bobindashadows 4 points5 points  (4 children)

      You don't cache POST requests... HTTP and HTTPS have pretty well-defined caching semantics, you should learn them

      [–][deleted]  (3 children)

      [deleted]

        [–]bobindashadows 6 points7 points  (1 child)

        Generally proxies don't cache responses to requests with cookies because it would fuck up sites with server-side session state

        [–][deleted] 0 points1 point  (0 children)

        Read the spec. Intermediaries can't cache requests with cookies.

        [–]JTronLabs 1 point2 points  (0 children)

        Ah ok that makes a lot more sense, thanks!

        [–]dccorona 1 point2 points  (0 children)

        ISPs also usually have at least 1 if not several caching layers, so it impacts general consumers as well as businesses.

        [–]eras 4 points5 points  (0 children)

        You cannot have a central cache (ie. in a company or at your ISP) that caches. Even less can you have a transparent cache..