Repository navigation
Block Chrome phone-home hosts without opening connections - #2573
Merged
Merged
Conversation
The phone-home hosts were mapped to 127.0.0.1, so Chrome still opened a connection for each request. If anything listened locally on that port, such as a dev server on 443, it received Chrome's background requests. Otherwise the connection was refused and Chrome kept retrying. ^NOTFOUND makes the host name lookup fail inside Chrome, so no connection is opened and no packet is sent. Assisted-by: Claude Opus 5.5 noreply@anthropic.com Change-Id: Idd33b1ec248f3debc52cac8621345dd2aa82c9fb
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The phone-home hosts were mapped to 127.0.0.1, so Chrome still opened a connection for each request. If anything listened locally on that port, such as a dev server on 443, it received Chrome's background requests. Otherwise the connection was refused and Chrome kept retrying.
^NOTFOUND makes the host name lookup fail inside Chrome, so no connection is opened and no packet is sent.
Assisted-by: Claude Opus 5.5 noreply@anthropic.com
Change-Id: Idd33b1ec248f3debc52cac8621345dd2aa82c9fb