Showing content from https://github.com/uBlockOrigin/uBlock-issues/issues/847 below:
"0" prefixes are currently not accepted as valid hosts entries · Issue #847 · uBlockOrigin/uBlock-issues · GitHub
Prerequisites
- I verified that this is not a filter issue
- This is not a support issue or a question
- I performed a cursory search of the issue tracker to avoid opening a duplicate issue
- Your issue may already be reported.
- I tried to reproduce the issue when...
- uBlock Origin is the only extension
- uBlock Origin with default lists/settings
- using a new, unmodified browser profile
- I am running the latest version of uBlock Origin
- I checked the documentation to understand that the issue I report is not a normal behavior
Description
Currently, 0 example.org
does not block the site, whereas ::1 example.org
, 127.0.0.1 example.org
and 0.0.0.0 example.org
does.
This is believed to affect the following lists:
This is to a certain extent related to #800, but does not seem to me to be a duplicate of it. I'm able to get :: example.org
to work in Nano but not in uBO, whereas 0 example.org
doesn't work in either of them.
A specific URL where the issue occurs
Depends on the site you'd want to block. For the examples above it's example.org
.
Steps to Reproduce
- Paste
0 example.org
in My Filters.
- Visit
example.org
.
- See that no page warnings show up, nor are the (few) on-site elements blocked.
Expected behavior:
A page warning shows up.
Actual behavior:
The site loads normally.
Your environment
- uBlock Origin version: 1.24.2
- Browser Name and version: Vivaldi 2.10.1745.23 64-bit
- Operating System and version: Windows 10 November 2019 Update
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4