Property 'session.timeout.auto.extend=false' is configured but browser still calls 'extend_session'
Written By
Solyom Nagy-Györkös
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
- In portal-ext.properties the following property
session.timeout.auto.extend=false is configured, however in the Network tab of the Developer Tools of the browser 'extend_session' is still being called.
Environment
- DXP 7.3
- DXP 7.2
- DXP 7.1
- DXP 7.0
Resolution
- Sessions are important for tracking attributes, such as attempts to log in to the portal, the locale of the user, the browser, or if the user is from a mobile device. Inter-portlet communication and portal-portlet communication also use session attributes. So whether a user is a guest or not, sessions provide important functionality to the portal.
- Based on this, there was an issue in the past where this behavior was discussed: LPS-47190, and the design choice is to extend sessions that expire instead of having permanent sessions. Having sessions that expire helps to reduce the server overhead by closing inactive sessions.
- If someone's goal is to reduce the calls to extend_session, it can only be done by increasing the
session.timeout property's value along with the same counterpart in web.xml.
Did this article resolve your issue ?