Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 6
    It appears then, that the general trend is towards allowing caching of HTTPS objects; this is normally a Good Thing, as developers should be telling the browser not to cache objects at all if they are privacy-sensitive, and allowing it to do so when they are not (e.g. images, css, which is very performance-benficial especially on HTTPS). Thanks for that. Commented Apr 22, 2010 at 20:44
  • 2
    Is it RFC-compliant to auto cache HTTPS resources without cache-control:public? Commented May 5, 2014 at 15:22
  • @Pacerier browsers consider RFC literal "request for comments". most often RFCs change to reflect what is already on browsers. Commented Oct 23, 2014 at 23:17