This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
WASM implementation sometimes fails to find rules #18589
Description
Type: code issue
With EASE enabled, http://meta.unix.stackexchange.com/ leads to the interstitial page while we would expect it to lead to https://unix.meta.stackexchange.com/ because of:
https-everywhere/src/chrome/content/rules/Stack-Exchange.xml
Lines 137 to 139 in b11aa25
I think this used to work. Am I missing something obvious here?
Reacted by Marek33
Activity
pipboy96 commentedon Oct 18, 2019
@Bisaloo I will try figuring this out.
cschanaj commentedon Oct 20, 2019
It is likely to be an issue with the way the WASM implementation handling the wildcards. It also affect browsing session outside of EASE since the last release
2019.6.27.[-]Rules don't work with EASE[/-][+]WASM implementation sometimes fails to find rules[/+]pipboy96 commentedon Oct 20, 2019
This is not EASE specific if I correctly understand, so I removed
EASElabel for now.cschanaj commentedon Oct 20, 2019
cc @zoracon @Hainish I have submit a PR at EFForg/https-everywhere-lib-core#1 relate to this issue on WASM module wildcard rules handling.
Hainish commentedon Nov 7, 2019
Fixed - thanks!