4 ms·
Great post! Not sure why giftyweddings.com needs to serve static files with an ETag in the HTTP response header: a hash of the file content is already included
by ngrilly 4y ago
Great post!
Not sure why giftyweddings.com needs to serve static files with an ETag in the HTTP response header: a hash of the file content is already included in the URL, which means it will invalidated when the content changes, just based on the path, regardless of the ETag.
- benhoyt 4y agoYeah, this is a good point. I've previously just used the "hash in the URL" approach as it seemed more obvious than ETag. I asked Ben Johnson why his hashfs library uses both, and he said "Yeah, that's a good point. I can't remember why I added both. I suppose some proxies may use ETag? I dunno."
- ngrilly 4y agoHaha. Fair enough. Thanks :)