https content is generally only cached in memory by the browser. But if the response contains a Cache-Control header that explicitly specifies that the content

https content is generally only cached in memory by the browser. But if the response contains a Cache-Control header that explicitly specifies that the content is public, it can be cached to disk, just like http content. Eg: Cache-Control: public, max-age=86400