-
Notifications
You must be signed in to change notification settings - Fork 6
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
Ipv6 from ipv4 transition addresses #6
Comments
These can be bad:
For example:
|
And there is still a chance to match |
https://regex101.com/r/2H0JLC/1
Test cases:
BenchmarkRead from bottom to top.
|
Why |
Because it was supposed to be ABP compatible. |
There are other instances of |
What do you mean by other instances? The list in this repo is just a draft for testing, it's already marked for removal. uAssets version is current and maintained by the team. BTW, even my version does not work in ABP, probably because of the header, still no one complains, so nothing to worry about. |
And dang :/ -
http://[::ffff:127.0.0.1]:8080/
is also valid https://en.wikipedia.org/wiki/IPv6_address#Transition_from_IPv4. Browser converts this tohttp://[::ffff:7f00:1]:8080/
. It will be::ffff:0000:0000
to::ffff:ffff:ffff
. Another regex?It seem unique (has unique application), so maybe||[::ffff:*]^
will be ok. Maybe not, but this is simple dec to hex translation - should not be hard to create good filter.The text was updated successfully, but these errors were encountered: