Differentiate logged-in sessions

[Ákos Gábriel, modificado hace 11 años.]

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, modificado hace 11 años.]

OK, looks like I've found a solution.

Akos
http://i-logic.hu

[Juan José García, modificado hace 7 años.]

Hi Akos.

I've the same problem, What's the solution?.

Thank you for your help.

Juanjo.

[David H Nebinger, modificado hace 7 años.]

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.