Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Different Browser Cache Behaviour on HTTPs Protocol in Google Chrome

Written By

Alexandra Rujzam

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Not all of the static requests are cached in Google Chrome, when you follow this documentation to set up HTTPs:
    Setting Up HTTPs on Tomcat

Reproduction steps:

  1. Set up the portal as per attached documentation
  2. Access the home page over 8443 port and observe the network tab in chrome browser
  3. Press F5 a few times
  4. Some of the static requests are cached, some are not, maybe only subsequently after pressing F5 several times
  5. Press Ctrl + F5
  6. Starts all over again, several refresh is needed, until all of them are cached

Environment

  • DXP 7.2
  • DXP 7.1
  • DXP 7.0

Resolution

Other than setting Cache-control headers, Liferay should not have any control over browser caches.

As we do not add no-cache header to the HTTPs responses, in other words we do not disable caching, we let the browser itself decide whether it caches the response or not.

Further tests and analysis showed that there is no difference between the two behaviours (HTTPs and HTTP) in Mozilla Firefox for example, thus this cannot be considered a Liferay bug.

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?