id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 26447,Deprecate USE_ETAGS setting in favor of ConditionalGetMiddleware unconditionally setting an ETag,Denis Cornehl,Denis Cornehl,"In my opinion this setting is not needed (any more) - Conditional-Get handling can happen in the ConditionalGetMiddleware, not in CommonMiddleware any more - using or not using the middleware is (nearly) the same as setting USE_ETAGS or not - ETag Calculation can happen also in the middleware this also will fix a problem when you use the GZipMiddleware in combination with the Conditional-Get handling in CommonMiddleware. Open questions for me: - ConditionalGetMiddleware also handles Last-Modified/If-Modified-Since , which CommonMiddleware didn't. I don't see a problem in throwing them together and activating/deactivating them together. You?",Cleanup/optimization,closed,HTTP handling,1.9,Normal,fixed,,k@…,Ready for checkin,1,0,0,0,0,0