You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
I am running the latest version
I checked the documentation and found no answer
I checked to make sure that this issue has not already been filed
Issue Details
AdGuard version:
v3 6.5
Filtering mode:
Local Vpn
Device:
Oneplus 7t
Operating system and version:
Android 11
Root access:
Yes
Expected Behavior
$removeparam should remove given parameters from specified domain URL
Actual Behavior
NO changes in the URL is observed in https post reqs
Screenshots
So the ookla speedtest app sends sensitive data line IMEI no. device fingerprint, phone tower area code etc to their servers. I want to block this by stripping off the tracking parameters from the URL.
The rule I created is this:-
||speedtest.net^$removeparam=/^(fingerprint|build_id|imei)=/
But it doesn't work. The URL is unmodified as displayed in filtering logs.
@ameshkov said that adguard can only modify document type https data in POST reqs, and will be improved later
Request to please fix this as soon as possible
Additional Information
Text me as "Ayan_c99" in telegram for screenshots. Although @ameshkov has all the info
@techIndia-hacker commented on Fri Dec 17 2021
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Issue Details
Expected Behavior
$removeparam should remove given parameters from specified domain URLActual Behavior
NO changes in the URL is observed in https post reqsScreenshots
Request to please fix this as soon as possible
Additional Information
Text me as "Ayan_c99" in telegram for screenshots. Although @ameshkov has all the info
@ameshkov commented on Mon Dec 20 2021
Applying $removeparam to POST requests is technically possible, but might be dangerous.
This issue should be moved to the CoreLibs repo and triaged there.
The text was updated successfully, but these errors were encountered: