- Mar 29, 2018
Thanks for the heads up on this.Latest ClearURLs update:
[1.19.0] - 2020-07-22
Changed url decoding to prevent endless loop
Same here. Updates are reviewed manually so it takes a bit of time sometimes. Already up to date on Chromium Edge.Thanks for the heads up on this.
On Firefox 'Check for updates' in the Add-ons Manager does not find this update. Ver 1.18.1 is the last update that was installed on June 10.
Currently available in Chrome Web Store only, which is stange since it's usually last to get updates.
- Added Dutch translation by Harm M.
- Changed url decoding to prevent endless loop
- Performance optimizations for rules by @thexeos
- Changed default rules and hash host to Github Pages
- Changed rules changelog button href to the new rules submodule repo
- Updated various translations - thanks to all contributors
I don't think he's figured out how to fix it. He has indicated "it's something with Chromium", as if there is no fix, which we know is incorrect.I think it still hasn't settled the eTag issue.
ClearURLs fails the eTag test at Cookieless Cookies. · Issue #67 · ClearURLs/AddonThat's weird. ClearURLs removes the ETag header, but Chromium somehow seems to store it anyway, so it doesn't matter if ClearURLs deletes it or not.
I have to investigate this again. Maybe it would help if I also remove the If-None-Match header. If it is no longer sent, it should theoretically not be possible to map it anymore with the ETag. However, this header is also used for POST requests to avoid duplicates. So here we need to make a distinction by request type. I don't know yet whether this is possible so easily.
I know about this problem. Unfortunately, the eTag filtering under Chrome does not work correctly at the moment. Under Firefox everything is cleaned up correctly. I have to find out why this is the case.