legacy-knowledge-base
公開されました Jun. 30, 2025

Same timestamp parameter value for the document URL is being shown for multiple requests

written-by

Koustuv Dhani

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

learn-legacy-article-disclaimer-text

Issue

  • Multiple requests show the same timestamp value ('t') in the document URL.

Environment

  • Liferay DXP 7.1+

Resolution

  • The t parameter in the URL represents a timestamp, the t parameter in Liferay URLs serves as a caching bypass mechanism. Its primary purpose is to ensure that when content changes, browsers or intermediaries fetch the latest version instead of relying on a cached copy.
  • How Does It Work?

    • The t parameter's value corresponds to the time of the content change (e.g., a new version of web content, document updates, etc.).

    • For example:

      • /document?file=abc&t=12 and /document?file=abc&t=35 are treated as different URLs.

      • If the version  t=12 was cached, accessing the URL with t=35 result in a cache miss and trigger a fresh fetch from the source.

    • The parameter is automatically updated by Liferay when content is modified.

  • Frequency of Change

    • The t parameter changes only when the associated content is modified or updated.

    • It does not operate on a timer or reset periodically. The value is tied strictly to the timestamp of the last content change.

  • Uniqueness Across Users and Devices

    • The t parameter is not unique to specific users or devices.

    • Its value is based solely on the file or content's modification time and serves as a caching strategy rather than a user-specific identifier.

  • Duplicate Timestamps

    • Multiple pages or assets can share the same timestamp, especially if they are updated simultaneously or originate from the same module (e.g., themes or JavaScript files built together).

    • This does not affect functionality, as each file's uniqueness is determined by its name and path in addition to the t parameter.

 

did-this-article-resolve-your-issue

legacy-knowledge-base