Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] $removeheader #2156

Closed
8 tasks done
mtxadmin opened this issue Jun 25, 2022 · 3 comments
Closed
8 tasks done

[Feature Request] $removeheader #2156

mtxadmin opened this issue Jun 25, 2022 · 3 comments
Labels
enhancement New feature or request invalid not a uBlock issue

Comments

@mtxadmin
Copy link

mtxadmin commented Jun 25, 2022

Prerequisites

I tried to reproduce the issue when...

  • uBO is the only extension
  • uBO with default lists/settings
  • using a new, unmodified browser profile

Description

Is it possible to implement $removeheader parameter?

https://kb.adguard.com/en/general/how-to-create-your-own-ad-filters#removeheader-modifier

Related issues, discussions and docs:

A specific URL where the issue occurs

Steps to Reproduce

Expected behavior

HTTP headers removed
(or even replaced?)

Actual behavior

HTTP headers stay as is

uBlock Origin version

Browser name and version

Operating System and version

@krystian3w
Copy link

krystian3w commented Jun 26, 2022

https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#response-header-filtering (seems to be new $queryprune -> $removeparam ? And there are only four headers can be removed)

No, response header was rare used without(/ not as) removeparam and should still works (so no removed form uBo arsenal):

Maybe uAssets are open to add needed new ^responseheader after correct report and no possible fix problem with other way (block page by $doc or $all maybe is last choice e.g. too many malware on server for problematic pages).

@gwarser gwarser added the enhancement New feature or request label Jun 26, 2022
@gwarser
Copy link

gwarser commented Jun 26, 2022

What is YOUR issue, and how it can be reproduced?

@gwarser gwarser added the invalid not a uBlock issue label Jun 26, 2022
@gwarser gwarser closed this as completed Jun 26, 2022
@HardenedSteel
Copy link

why this issue is closed? the issue is ublock origin doesn't have $removeheader

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request invalid not a uBlock issue
Projects
None yet
Development

No branches or pull requests

4 participants