-
Notifications
You must be signed in to change notification settings - Fork 78
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
Add queryjump to redirect url #3206
Comments
Here too:
it was declined in the past, but yes, it then had been mentioned to be reconsidered over time as per : #1784 (comment) |
Related issue: uBlockOrigin/uBlock-issues#3206 The main purpose is to bypass URLs designed to track whether a user visited a specific URL, typically used in click-tracking links. The `urlskip=` option ... - ... is valid only when used in a trusted filter list - ... is enforced only on top documents - ... is enforced on both blocked and non-blocked documents - ... is a modifier, i.e. it cannot be used along with other modifier options in a single filter The syntax is `urlskip=[steps]`, where steps is a space-separated list of extraction directives detailing what action to perform on the current URL. The only supported directive in this first commit is `?name`, which purpose is to extract the value of a named URL parameter and use the result as the new URL. Example: ||example.com/path/to/tracker$urlskip=?url The above filter will cause navigation to https://example.com/path/to/tracker?url=https://example.org/ to automatically bypass navigation to `example.com` and navigate directly to https://example.org/ It is possible to recursively extract URL parameters by using more than one directive, example: ||example.com/path/to/tracker$urlskip=?url ?to More extraction capabilities may be added in the future.
Test cases: Filters:
Navigate to Navigated to: Filter:
Navigate to Navigated to: Filter:
Navigate to Navigated to Note: No skip occurred since not all extraction directives could be fulfilled |
Spaces before "?" are needed? |
Yes. Commit message:
In the future we might want to add base64-decoding or regex extraction ( |
Hi, when I want to reach
I wrote a filter rule as |
I think the parameter value should be a valid string to use with new URL("hepsiburada.com/philips-ca6700-10-espresso-machine-kirec-temizleme-solusyonu-p-HBCV00002YNJSF") will return error, so no, you can't use |
So what kind of filter rule should I write for this? |
That is not a valid
However as @stephenhawk8054 pointed out, the extracted string is not a valid URL as per URL API, so it does not work in the end. I do think it should work though, so I will see what can be done about it. |
When present, the `+https` directive will force the protocol of the resulting URL to be `https:`. Related feedback: uBlockOrigin/uBlock-issues#3206 (comment)
In the next dev build, this should work:
|
Works fine for me (Firefox & Chromium). |
Prerequisites
I tried to reproduce the issue when...
Description
Mentioned in #760 (comment) #2476 (comment) and now it should be possible to implement as a trusted network filter modifier. It's similar to
$uritransform
except that this should redirect to different domain and complementshref-sanitizer
. Maybe$to
or something can be combined to restrict the domain to redirect rather than always blindly trust the url in parameter. Though the original context was about shortners, I rather want to use this to automate skip of strict-block page which is currently possible only by manual click.A specific URL where the issue occurs.
`https://ouo.io/s/BulJXu78?s=http://hackstore.link/alg2i`
Steps to Reproduce
NA
Expected behavior
NA
Actual behavior
NA
uBO version
1.57.0
Browser name and version
Not relevant
Operating System and version
Windows 10
The text was updated successfully, but these errors were encountered: