4 ms·
Unless I'm mistaken, that's not true. The hash is computed from the full path and the prefix is the first 32-bits of the hash (or 48-bits if using Safe Browsing
by dpkonofa 7y ago
Unless I'm mistaken, that's not true. The hash is computed from the full path and the prefix is the first 32-bits of the hash (or 48-bits if using Safe Browsing).
- bigiain 7y agoLooks right. From your links upthread to Google's Safe Browsing API docs: Canonicalize("http://www.evil.com/blah#frag" http://www.evil.com/blah#frag") = "http://www.evil.com/blah"; http://www.evil.com/blah"; Canonicalize("http://evil.com/foo?bar;" http://evil.com/foo?bar;") = "http://evil.com/foo?bar;"; http://evil.com/foo?bar;"; So fragments get dropped (as expected) buy query params do not (also, in retrospect, what I'd expect to make it work at all...) So https://news.ycombinator.com/reply?id=21254732 https://news.ycombinator.com/reply?id=21254732 will not end up hashing "https://ycombinator.com" https://ycombinator.com", but the whole thing including the path and query string.