Foros de discusión

Session Cookie path attribute not set

Kruttika Phalke, modificado hace 7 años.

Session Cookie path attribute not set

New Member Mensajes: 11 Fecha de incorporación: 22/04/13 Mensajes recientes
Anybody having idea how to set Session Cookie path attribute in liferay 6.0 or 6.1 application ?
thumbnail
Olaf Kock, modificado hace 7 años.

RE: Session Cookie path attribute not set

Liferay Legend Mensajes: 6403 Fecha de incorporación: 23/09/08 Mensajes recientes
Kruttika Phalke:
Anybody having idea how to set Session Cookie path attribute in liferay 6.0 or 6.1 application ?


Check the application server you're using. Liferay just starts a session, the appserver provides the underlying mechanics to introduce a session cookie.
Kruttika Phalke, modificado hace 7 años.

RE: Session Cookie path attribute not set

New Member Mensajes: 11 Fecha de incorporación: 22/04/13 Mensajes recientes
Olaf Kock:
Kruttika Phalke:
Anybody having idea how to set Session Cookie path attribute in liferay 6.0 or 6.1 application ?


Check the application server you're using. Liferay just starts a session, the appserver provides the underlying mechanics to introduce a session cookie.



M using apache tomcat
thumbnail
Artur Linhart, modificado hace 7 años.

RE: Session Cookie path attribute not set

Expert Mensajes: 459 Fecha de incorporación: 13/09/07 Mensajes recientes
Perhaps this could help you:
"sessionCookiePath

The path to be used for all session cookies created for this context. If set, this overrides any path set by the web application. If not set, the value specified by the web application will be used, or the context path used if the web application does not explicitly set one. To configure all web application to use an empty path (this can be useful for portlet specification implementations) set this attribute to / in the global CATALINA_BASE/conf/context.xml file.

Note: Once one web application using sessionCookiePath="/" obtains a session, all subsequent sessions for any other web application in the same host also configured with sessionCookiePath="/" will always use the same session ID. This holds even if the session is invalidated and a new one created. This makes session fixation protection more difficult and requires custom, Tomcat specific code to change the session ID shared by the multiple applications."

See Tomcat documentation
https://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Context_Parameters