Henrik Nordstrom wrote:
How ETag:s is generated is extremely server dependent, and not guaranteed to be unique across different URLs. You can not at all count on two files having the same ETag but different URLs to be the same file, unless you also is responsible for the server providing all the URLs in question and know that the server guarantees this behavior of ETag beyond what the HTTP specification says.
Exactly - this is the case here.The problem that is being solved is when a server serves the same file, within the same server, but at multiple different URLs. The file in this case is interpreted as a different file each time, and is cached over and over again.
Obviously such a feature wouldn't be something you would switch on by default, and the admin would be expected to know what he is doing when they switch this behaviour on.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
