0410a26c2d
The NetworkIsolationKey determine's what site's DNS cache shard is used for DNS lookups, and what requests can share a socket when using an H2/QUIC proxy. Also make Jingle and GCM pass in a NetworkIsolationKey that matches the URL they're connecting to. This will currently only leak DNS of the host they're looking up to top frames navigated to that same host, which seems fine (though once WebRTC is using NIKs, too, this will mean web-initiated WebRTC tunnels and GCM/Jingle tunnels to the same hos will share H2/QUIC proxy connections, which allows more interesting, but not too concerning leaks) Bug: 1082280 Change-Id: I4625327940dc3b2ec4022f7e0937a5fec51634b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209407 Reviewed-by: Shivani Sharma <shivanisha@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by: Dmitry Titov <dimich@chromium.org> Reviewed-by: Zhongyi Shi <zhongyi@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#774866}