HTTP Header - Permissions-Policy - attribution-reporting
|
Jun. 25, 2024, 09:03 PM
Post: #1
|
|||
|
|||
HTTP Header - Permissions-Policy - attribution-reporting
Anyone know if it is possible for Proxo to get "attribution-reporting" spoofed/bypassed?
For example, my only web browser is Ungoogled Chromium v114. v114! I would highly prefer to not go any newer! I've bumped into only one web site that I cannot get to work with v114. It is -- https://reg.usps.com/login You DO NOT NEED AN ACCOUNT. Just type in a RANDOM username and a RANDOM password. You will see the "unrecognized feature: attribution-reporting" in the error console. Can a Proxo header filter spoof/bypass this? This "feature" is something added in v117 - https://caniuse.com/mdn-http_headers_per...-reporting But again, I want to stick with v114 (if possible). |
|||
Jun. 30, 2024, 01:46 AM
Post: #2
|
|||
|
|||
RE: HTTP Header - Permissions-Policy - attribution-reporting
RANDOM username and a RANDOM password does not return "unrecognized feature: attribution-reporting" in the error console for this Opera. I see "We are unable to process your request at this time. Please try again..." under the password field.
Are you spoofing your user-agent to mimic v117 or younger? If so, try with a user-agent that doesn't support this feature. You could also try removing all the related headers. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Attribution-Reporting-Eligible shows Attribution-Reporting-Eligible (out), and Attribution-Reporting-Register-Source (in) or Attribution-Reporting-Register-Trigger (in) So Code: [HTTP headers] URL match is optional. Used to add notes. The ` lets me display only the filters that I have added. More at https://developer.mozilla.org/en-US/docs/Web/API/Attribution_Reporting_API |
|||
![]() ProxRocks |
« Next Oldest | Next Newest »
|