: Use - or misuse - of ETags I'm using an application that sets ETags by md5()ing the URL. As I understand it, that's quite insane. In effect, it means that content for a specific URL won't
I'm using an application that sets ETags by md5()ing the URL. As I understand it, that's quite insane. In effect, it means that content for a specific URL won't be fetched anew ... ever. Unless a hard-refresh is sent or, maybe, the browser is restarted (yet to test the latter).
Is this abuse of the ETag header?
More posts by @Megan663
1 Comments
Sorted by latest first Latest Oldest Best
Well, if the content never, ever changes, then I guess it would be OK. Otherwise... no.
Of course, browsers will still need to contact the server (using a conditional GET request) to determine whether the content has changed, so it's not quite as bad as, say, setting an Expires date too far in the future: as soon as you fix the application to use ETags correctly, the old URL-based ETags will no longer match and everything will work normally.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.