- Added #284
- Added #56
- Fixed#241
- Possible fix & workaround for #203
- Fixed bug in "history tracking injection protection". This option was not disabled, when the global filter switch are on off
- Added an option to im-/export the log (requires the `downloads` permission)
- Added an option to im-/export the settings (requires the `downloads` permission)
- Added information page for blocked sites, when they are called in the `main_frame`
- Added "multiple times URL encodes" recognition
- Refactoring
- Changed background script loading sequence to prevent that required functions are not yet loaded.
+ Changed the regex interpretation for better performance.
+ Also asked for "unlimitedStorage" permission to have enough space for user generated rules.
Lately, I have received relatively few requests with potentially bad URLs. On the one hand, that could be because ClearURLs are working very well by now. But I also think that not everyone wants to sign up to GitLab to report a URL. That's why I've added a new button that reports the current URL in the active tab to me, so I can take a closer look at the URL.
So that you can see exactly what data will be sent to me, I have uploaded the source code for the PHP script, of course, without a password etc.
Please be careful not to send URLs with personal information or tokens.
The splitt function for the fields was a greedy function and splitt at the last question mark, but it should splitt at the last question mark. So now the splitt function is a non-greedy function.
I've updated the ClearURLs core, so that ClearURLs only cleans the fields from urls.
This means that ClearURLs can no longer examine all components of a URL and, if necessary, remove something, but only the so-called GET fields.
This restricts not hardly, since everything that is not a GET field is a part of the url (the path) and should not actually be removed.
However, because ClearURLs was able to remove these path elements, this problem came up again. Now ClearURLs can only remove GET fields and thus no longer destroy paths.
I hope that there are fewer problems now. Another little side effect of the change, ClearURLs is now working more efficiently.
