mirror of
https://github.com/gorhill/uBlock.git
synced 2026-03-11 09:04:36 +00:00
408b538e75
Related issue: https://github.com/uBlockOrigin/uBOL-home/issues/157 The `header=` option will be converted into DNR's `responseHeaders` condition. There will be an attempt to convert regex-based values into DNR- compatible syntax. Not all regex-based patterns can be converted to use DNR's patterns with `*` and `?` special characters. The implementation of `header=` option in uBO has been revisited to improve compatibility with DNR syntax to minimize burden for list maintainers when creating `header=` filters compatible with both uBO and uBOL. The changes: - Header names are now case-insensitive by default - Occurrences of `*` in non-regex-based header values now mean "matches any number of characters" - Occurrences of `?` in non-regex-based header values now mean "matches zero or one character" At time of commit, and as per MDN, only Chromium-based browsers currently support filtering on repsonse headers: https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/declarativeNetRequest/HeaderInfo Also as per MDN, Chromium 121-127 silently ignore the `responseHeaders` condition, potentially causing undue blocking of network requests. Currently uBOL support Chromium 122 and later, meaning we need to mind potential false positives in Chromium 122-127 for filters using `header=` option. |
||
|---|---|---|
| .. | ||
| _locales | ||
| css | ||
| img | ||
| js | ||
| lib | ||
| web_accessible_resources | ||
| 1p-filters.html | ||
| 3p-filters.html | ||
| about.html | ||
| advanced-settings.html | ||
| asset-viewer.html | ||
| background.html | ||
| blank.html | ||
| cloud-ui.html | ||
| code-viewer.html | ||
| dashboard.html | ||
| devtools.html | ||
| document-blocked.html | ||
| dyna-rules.html | ||
| logger-ui.html | ||
| no-dashboard.html | ||
| popup-fenix.html | ||
| settings.html | ||
| support.html | ||
| whitelist.html | ||