News for hackers. Stuff that matters.

A comment on Compression Dictionary Transport. Parent comment

Re:Compression Dictionary Transport by pornel on Monday September 16, 2024 @04:52PM (#41560755)
Apart from tracking, the other concern is reliability — the server may lose or change the file, and this may not be noticed when clients use the hash, until the hash stops being popular, and you're left with a broken site.
[ Parent | on HN ]
Re:Compression Dictionary Transport by dexterdog on Monday September 16, 2024 @11:17PM (#41563724)
If you change the file the hash changes
[ Parent | on HN ]
Re:Compression Dictionary Transport by pornel on Tuesday September 17, 2024 @09:57AM (#41567659)
The hash is sent separately from the file. For it to change in the HTML and other places linking to it, there has to be some mechanism to update the links, and that is the part that can get out of sync or bitrot.
[ Parent | on HN ]
Re:Compression Dictionary Transport by dexterdog on Tuesday September 17, 2024 @06:51PM (#41573723)
Which is part of the security of the hash. When I embed a script on my site I get the hash at the time I test it. If the content changes without my knowledge it will not allow a replacement from the source. Assets are not overly cacheable if they don't change the location when the file changes.
[ Parent | on HN ]