Hi Tom,
If the view is login required, then you must send 'Vary: cookie',
> there is no option. Consider what would happen if you did not vary on
> the cookie:
>
> Logged in user accesses the page via a caching proxy
> Returned page is cacheable, no Vary header
> Proxy stores page in cache
> Not
On Wed, Mar 3, 2010 at 9:50 AM, Tamas Szabo wrote:
> Hi,
>
> I've just enabled caching for a Django application and it works great, but
> there is a small problem.
>
> As you know, Session middleware adds a Vary: Cookie header to the response
> and it is smart enough to do that only if the session
Hi,
I've just enabled caching for a Django application and it works great, but
there is a small problem.
As you know, Session middleware adds a Vary: Cookie header to the response
and it is smart enough to do that only if the session has been accessed.
This is all good, but the problem is that I
