Code

Changes between Version 1 and Version 2 of Ticket #15201, comment 6


Ignore:
Timestamp:
01/20/13 13:13:11 (15 months ago)
Author:
aaugustin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15201, comment 6

    v1 v2  
    77This leaves us with Carl's idea of "cache anything that doesn't have Vary: Cookie" — but is it even useful? 
    88 
    9 Caching is hard! 
     91) Very few websites will match this requirement. Most websites indicate when a user is logged in. Many show a login form on every page for anonymous users, making anonymous pages depend on the cookie (because of the CSRF token). 
     10 
     112) Since it's purely HTTP-level, it could be done by a caching reverse proxy. For instance, Varnish seems [https://www.varnish-cache.org/docs/3.0/tutorial/cookies.html way more capable] of dealing with this than Django. 
     12 
     13---- 
     14 
     15So, I'm +1 for deprecating this feature.