Vista combinada Visión Plana Vista de árbol
Discusiones [ Anterior | Siguiente ]
toggle
Ákos Gábriel
Differentiate logged-in sessions
11 de septiembre de 2012 23:10
Respuesta

Ákos Gábriel

Ranking: Junior Member

Mensajes: 33

Fecha de incorporación: 5 de octubre de 2009

Mensajes recientes

Hi,

I'm trying to configure Varnish (reverse proxy) for our portal. For guest sessions (not logged in) it works perfectly. However I need to disable caching for logged-in sessions (for obvious reasons).

Now this doesn't seem to work.

Varnish can decide based on information being in the HTTP header:

- request type (post,get,...)
- request url
- cookies present

Varnish can also put cookies into the response header so once varnish detected a session is logged in, it can track that throughout the full lifetime of the session.

Thanks for any help/hint.

Akos
http://i-logic.hu
Ákos Gábriel
RE: Differentiate logged-in sessions
12 de septiembre de 2012 10:20
Respuesta

Ákos Gábriel

Ranking: Junior Member

Mensajes: 33

Fecha de incorporación: 5 de octubre de 2009

Mensajes recientes

OK, looks like I've found a solution.

Akos
http://i-logic.hu
David H Nebinger
RE: Differentiate logged-in sessions
23 de noviembre de 2016 13:41
Respuesta

David H Nebinger

Community Moderator

Ranking: Liferay Legend

Mensajes: 13011

Fecha de incorporación: 1 de septiembre de 2006

Mensajes recientes

I don't understand the original premise, that you can't cache when a user is logged in.

Varnish does, after all, respect the cache control headers in the response from the portal. The portal does not allow caching for dynamic content, so any page rendered for me will not be cached and when you ask for the same page you'll see your page and not mine.

So basically only static assets (images, js, css) will likely be cached, and none of those things should change between authenticated users.