Impersonation Clashes with Cached Web Content Templates
Written By
Orsolya Hegedus
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
- Web Content Templates can be configured for caching to boost performance.
- When not cached, the generated HTML is rendered for each request. When cached, the generated HTML is stored in the cache and reused for all subsequent requests until the cache entry is cleared or expires.
- However, impersonation introduces a conflict. The rendered HTML differs for users who are impersonated because the URLs include the ?doAsUserId parameter.
- In this scenario, it might happen that either the impersonating user or regular users might see incorrect links, specifically when the cache is refreshed by one user type while the other is viewing the page.
Resolution
- The observed behavior is expected due to the caching mechanism. The template, once rendered, is cached and served as-is for subsequent requests. Impersonation changes the URL, but the cached version doesn't reflect this change, leading to incorrect links.
- To prevent this issue, disable template caching, especially when impersonation is active.
Did this article resolve your issue ?