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
I believe Sec-* headers are considered "restricted" and cannot be set by standard fetch, but I am not sure if they are allowed to be set by extensions. Is it possible to spoof these headers as well? It may increase the effectiveness of ad "clicking".
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I was curious about how this extension performed network requests. According to Firefox devtools, network requests are sent with:
whereas "normal" cross-origin navigate is sent with:
The purpose of these headers appears to be to indicate how the request was performed (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Mode). Ad networks may filter "fraud" requests using these headers, as "cors" (for example) is not expected for ad clicks.
I believe
Sec-*
headers are considered "restricted" and cannot be set by standard fetch, but I am not sure if they are allowed to be set by extensions. Is it possible to spoof these headers as well? It may increase the effectiveness of ad "clicking".Beta Was this translation helpful? Give feedback.
All reactions