> When I enable etags, django is sending back an etag on 404 pages. > When a client does a subsequent request for the same nonexistent > page, a 304 response is sent back, because the page has not changed > (based on the etag). > > When I disable etags, multiple requests for a non existent page all > return 404 as expected. > > Is there a way to disable etag generation on 404 pages, while still > performing it on all 'real' pages?
I guess the simplest thing would be to write a middleware class, that inherits the conditional get middleware, overloads the method and simply add a condition, that checks the status code of the response. If it's 404, remove the Etag. Then use that middleware instead of the normal one. I think the behaviour is correct though, why do you want to redefine it ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
