掲示板
Differentiate logged-in sessions
11年前 に Ákos Gábriel によって更新されました。
Differentiate logged-in sessions
Junior Member 投稿: 33 参加年月日: 09/10/05 最新の投稿
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
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
11年前 に Ákos Gábriel によって更新されました。
RE: Differentiate logged-in sessions
Junior Member 投稿: 33 参加年月日: 09/10/05 最新の投稿
OK, looks like I've found a solution.
Akos
http://i-logic.hu
Akos
http://i-logic.hu
7年前 に Juan José García によって更新されました。
RE: Differentiate logged-in sessions
New Member 投稿: 1 参加年月日: 15/07/28 最新の投稿
Hi Akos.
I've the same problem, What's the solution?.
Thank you for your help.
Juanjo.
I've the same problem, What's the solution?.
Thank you for your help.
Juanjo.
7年前 に David H Nebinger によって更新されました。
RE: Differentiate logged-in sessions
Liferay Legend 投稿: 14919 参加年月日: 06/09/02 最新の投稿
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.
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.