Skip to content
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

RFE: whitelisting hosts could be more intuitive #145

Closed
jpjp opened this issue Apr 27, 2015 · 2 comments
Closed

RFE: whitelisting hosts could be more intuitive #145

jpjp opened this issue Apr 27, 2015 · 2 comments

Comments

@jpjp
Copy link

jpjp commented Apr 27, 2015

e.g. the traffic monitor says that xyz.abc.amazon-images.com is blocked

I enter amazon-images into the whitelist: it doesn't help.
I try .amazon-images.com: invalid hostname
I try ||amazon-images.com like in the monitor: invalid hostname
I try *amazon-images.com/
: it's accepted, but it doesn't help. Also: this would probably block not-amazon-images.com, which I didn't mean.

So I gave up in the end and just clicked the button to whitelist all of amazon.
Maybe a few examples below the textarea.

@scronide
Copy link

Looks like you were over-thinking it and the one thing you didn't try was just amazon-images.com (FWIW, I think the actual domain is images-amazon.com)

@gorhill
Copy link
Owner

gorhill commented Apr 27, 2015

I enter amazon-images into the whitelist: it doesn't help.

Whitelist pane says:

Your list of host names for which uBlock₀ will be disabled

What you want is an exception filter:

@@||amazon-images.com^

Put that in the My filters pane.

@gorhill gorhill closed this as completed Apr 27, 2015
geoffdutton pushed a commit to geoffdutton/uBlock that referenced this issue Apr 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants