-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Test domain against filter lists in extension #3362
Comments
This comment was marked as abuse.
This comment was marked as abuse.
The above is a discussion, which is why when I did a "cursory search" for simillar issues I didn't find anything. To be clear I didn't see that discussion until you linked it. You seem to be very agressive toward me, but I will take that as potentially a language barrier. From now on I request that you please assume good faith from me. |
This comment was marked as spam.
This comment was marked as spam.
@krystian3w if I understand what you are saying, my one critique of that is that an isolated env. is going to be far more effort to spin up one for maybe a couple of domains in my use case (writing a few rules at a time). |
This comment was marked as off-topic.
This comment was marked as off-topic.
Maybe someone can advise you on how to pretend that there is network traffic without deactivating the network card and real tabs with address bar (maybe commands to standard devtools). |
This comment was marked as off-topic.
This comment was marked as off-topic.
In the meantime, a workaround to test various URLs is to use the format used by the {"frameUrl":"https://www.guildwars2.com/en/","url":"https://www.google-analytics.com/analytics.js","cpt":"script"}
Set When the content of the JSON file is changed, best to restart uBO to ensure is not using the older version as it holds onto the last loaded version for a while to avoid overhead of reloading the file everytime we click benchmark/report buttons. |
Related issue: uBlockOrigin/uBlock-issues#3362 There used to be a way to test URL against the network filtering engine, but this was removed in a distant past during refactoring. The ability has been brought back through uBO's own developer tools, accessible through the _More_ button in the _Support_ pane in the dashboard. To query the static network filtering engine, enter the following in the text editor: snfe?url-to-test [type] [url-of-context] `snfe?` is a prompt indicating the intent to query the static network filtering engine. At a minimum there must be a URL to test. Optionally the type of the resource to match, default to `xhr` if none specified. Also optionally, the context from within which the request is made. Example: Enter: snfe?https://www.google-analytics.com/analytics.js Result: url: https://www.google-analytics.com/analytics.js blocked: ||google-analytics.com^ Enter: snfe?https://www.google-analytics.com/analytics.js script Result: url: https://www.google-analytics.com/analytics.js type: script blocked: ||google-analytics.com^ modified: ||google-analytics.com/analytics.js$script,redirect-rule=google-analytics_analytics.js:5 Enter: snfe?https://example.com/ Result: url: https://example.com/ not blocked Enter: snfe?https://example.com/ ping Result: url: https://example.com/ type: ping blocked: *$ping,3p
This can now be done in dashboard => Support => More button, by using the Please refer to commit message for usage: gorhill/uBlock@b7ed3b45ed |
Prerequisites
I tried to reproduce the issue when...
Description
I would like to test a simple list I have written, to see if the domain(s) I want to block and not to block are working as intended. Ideally I'd like to not actually visit e.g. a malware or phishing domain if all I want to do is block it and ensure that the extension is working correctly
A specific URL where the issue occurs.
ANY
Steps to Reproduce
Expected behavior
Actual behavior
oops, I visited the site, accidentally because the list was written wrong.
uBO version
Latest (1.59.0 as of writing)
Browser name and version
Any
Operating System and version
Any
The text was updated successfully, but these errors were encountered: