`$removeparam=_xts_` internally become the literal Translated and are unlikely to work properly in uBO.įor example, the `queryprune` value of a filter such as Which are special regex characters won't be properly This means `removeparam=` with characters Regex expression (leaving out the documented specialĬharacters). `queryprune=` values are always assumed to be literal UBO does not escape special regex characters since the Uppercase characters in `queryprune=` values. No need to ask for case-insensitivity, and no need to use UBO always matches in a case insensitive manner, there is Point, but reasonable compatibility should be achieved forĪ majority of instances of `removeparam=`. It is not possible to achieve perfect compatiblity at this The following new and recently added filter options are not compatible with Is no longer an issue ever since uBO redirects to local resources through The legacy code to test for spurious CSP reports has been removed. ThisĬan be used to remove all query parameters EXCEPT those who match the If the `queryprune=` value starts with `!`, the test will be inverted. This ensures a better future compatibility with AdGuard's (including `_`), the value will be internally converted to regex equivalent If the `queryprune=` value is made only of alphanumeric characters The following changes have been implemented: To be decided: to restrict usage of this filter option to only uBO's own Provided eventually if ever it is decided to move it from experimental to More documentation justifying the purpose of `header=` option will be Important: It is key that filter authors use as many narrowing filter optionsĪs possible when using the `header=` option, and the `header=` option shouldīe used ONLY when other filter options are not sufficient. will override the block `header=`ĭynamic filtering's `allow` rules override block `headers=` filters. Generic exception filters can be used to disable specific block `header=`įilters, i.e. Just a matter of specifying the header name without a header value: To block a network request if it merely contains a specific HTTP header is to anchor to end of string, use trailing `|`, not `$` to anchor to start of string, use leading `|`, not `^` The header value is assumed to be a literal regular expression, except for The matches are always performed in a case-insensitive manner. has a response HTTP header named `via`, which value matches the regular is not strictly 1st-party to the context The above filter is meant to block network requests which fullfill all the Header is present and whether it matches or does not match a specific value. Toggling `filterOnHeaders` to `true` in advanced settings.Ībility to filter network requests according to whether a specific response To prevent mistakenly using `1P` or `3P` where weak partyness is meant to beĬurrently experimental and under evaluation. The strict partyness options will be visually emphasized in the editor so as Network request will be considered 1st-party if and only if both the context The new partyness options are meant to check for strict partyness, i.e. Network request is considered 1st-party to its context as long as both theĬontext and the request share the same base domain. The current options 1p/3p are meant to "weakly" match partyness, i.e. Operating System and version: Windows 10 October 2020 Update.$removeparam is treated as being $queryprune Actual behavior: See that the logger considers all its entries to be an Invalid network filter in.This would save me from having to maintain and sync two different versions of that list, one for uBO and one for AdGuard. I therefore propose that they should be made into aliases of each other. ![]() $removeparam does not seem to need | in its values.AdGuard removes the parameters at the network level instead of in the URL bar. ![]() ![]() However, those two $ qualifiers seem to me to do the exact same thing, with only 2 current exceptions: But during some syntax checking of regional lists, I discovered that $queryprune seems to have been added to uBO. I've been working on for some weeks now, which I did while presuming that only AdGuard had a feature to remove $/& parameters from URLs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |