Any reason not to use USE_ETAGS with CommonMiddleware in Django?
Posted
by allyourcode
on Stack Overflow
See other posts from Stack Overflow
or by allyourcode
Published on 2010-05-02T00:34:58Z
Indexed on
2010/05/02
0:37 UTC
Read the original article
Hit count: 196
The only reason I can think of is that calculating ETag's might be expensive. If pages change very quickly, the browser's cache is likely to be invalidated by the ETag. In that case, calculating the ETag would be a waste of time. On the other hand, a giving a 304 response when possible minimizes the amount of time spent in transmission. What are some good guidelines for when ETag's are likely to be a net winner when implemented with Django's CommonMiddleware?
© Stack Overflow or respective owner