With self-signed SSL certificates, Chrome ignores all caching directives and reloads the content.


In a non-production environment (or pre-golive production environment), you are using an invalid or self-signed SSL certificate. You notice that when accessing the site via https, no responses from the web server (AEM dispatcher) are getting cached in Chrome browser.

Even if you have set Cache-Control: max-age=... header and Last-Modified header is present, you still don't observe any caching. Also, you observe that the If-Modified-Since request header isn't sent from the Chrome browser when the same file is loaded again.


This is a known issue with Chrome browser.  It does not cache responses if the HTTPS connection is using an invalid Certificate.  See this bug report for details:


Either purchase and install a proper SSL certificate or test the caching via http instead of https.

تم ترخيص هذا العمل بموجب الترخيص العام غير المعدل الخاص بالإسناد وعدم التجارة والمشاركة الإصدار 3.0 ‏من ‏‏Creative Commons‏‏  إن بنود Creative Commons لا تشمل منشورات Twitter™‎ وFacebook.

إشعارات قانونية   |   سياسة الخصوصية على الإنترنت