django - What causes the if-none-match request header field to become huge? -


i have problem if-none-match header sent django cms app, running through apache2/mod_wsgi.

when editing used page, various users' browsers (chrome , ff) error apache complaining if-none-match field long.

on inspection (through wireshark) browser sending 8kib if etags in 1 header line. clearing browser's cache or restarting not clear problem.

i'm not sure @ fault here.

is correct interpretation of field's values follows:

the browser claiming know few hundred previous versions of page (which credible, error occurs on heavily 'get'ed rapidly-changing pages).

is there way of clearing out etags ff or chrome?

thanks,

chris.

it may best prevent django generating etags in first place. since django generates them after page has rendered, don't save server resources--just bandwidth. if bottleneck isn't bandwidth, can disable them setting use_etags = false in settings file.

details here: http://docs.djangoproject.com/en/1.2/ref/settings/#std:setting-use_etags


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -