Show source of host blacklisting #526

dag commented 2016年03月18日 16:30:36 +01:00 (Migrated from github.com)

My apologies if this has been discussed previously; I could find no relevant issues.

I'd like to be able to see where a blacklisting of a hostname is coming from, i.e. which hosts file or I suppose, which local rule. The logical place for this would be in the logger, as in uBlock, although I would certainly not mind some way to see this in the matrix itself if the UI could allow for it sensibly (not sure).

Optimally I'd like to know all hosts files a hostname is in, since there is often quite a bit of overlap, but knowing one source would be preferable over not knowing anything. I can understand if uMatrix isn't storing that information, for efficiency, but perhaps it could simply scan all active hosts files when you ask for this, since it won't be something happening all the time in the background or without user interaction? I think it's fine if clicking for more details about a request in the logger is comparably slow.

This would go particularly well with #525 giving you a way to see the hpHosts classification of a hostname, and would also be useful for debugging false-positives and tell you which hosts file to possibly disable.

edit:

It would also be very useful if this information was listed on the block notice page for 1st-party requests.

My apologies if this has been discussed previously; I could find no relevant issues. I'd like to be able to see where a blacklisting of a hostname is coming from, i.e. which hosts file or I suppose, which local rule. The logical place for this would be in the logger, as in uBlock, although I would certainly not mind some way to see this in the matrix itself if the UI could allow for it sensibly (not sure). Optimally I'd like to know all hosts files a hostname is in, since there is often quite a bit of overlap, but knowing one source would be preferable over not knowing anything. I can understand if uMatrix isn't storing that information, for efficiency, but perhaps it could simply scan all active hosts files when you ask for this, since it won't be something happening all the time in the background or without user interaction? I think it's fine if clicking for more details about a request in the logger is comparably slow. This would go particularly well with #525 giving you a way to see the [hpHosts classification](http://hosts-file.net/?s=classifications) of a hostname, and would also be useful for debugging false-positives and tell you which hosts file to possibly disable. _edit:_ It would also be very useful if this information was listed on the block notice page for 1st-party requests.

JeffCarpenter commented 2019年11月10日 23:47:08 +01:00 (Migrated from github.com)

@gorhill would you be open to PRs for this feature?

@gorhill would you be open to PRs for this feature?

arek commented 2026年06月18日 22:33:58 +02:00

The extension merges all selected hosts files into a single HNTrieContainer binary trie, once a hostname is inserted, the record of which file it came from is gone. Could use OPs suggestion to scan lists but that could be slow depending on how many lists there are and how big they are.

Closing without a fix

The extension merges all selected hosts files into a single HNTrieContainer binary trie, once a hostname is inserted, the record of which file it came from is gone. Could use OPs suggestion to scan lists but that could be slow depending on how many lists there are and how big they are. Closing without a fix

arek commented 2026年06月19日 09:56:54 +02:00

Actually, I'll benchmark the performance first

Actually, I'll benchmark the performance first

arek commented 2026年06月19日 11:42:11 +02:00

Implemented it so that the user has to explicitly go in the details tab to show source to performance impact isnt a factor

Implemented it so that the user has to explicitly go in the details tab to show source to performance impact isnt a factor