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
This extension doesn't seem to be effective against a certain websites such as "open-vsx.org. The only way to get this website to recognize the custom useragent is via the Developer Tools on Chrome. This is definitely not a solution nor a workaround that needs to be adopted since it only works on the tab you set it for (as apposed to all the open tabs) and for that session only.
The text was updated successfully, but these errors were encountered:
Unless I'm misunderstanding - it looks like youngunix is right, using firefox's Network tab and loading the site, there's the odd request header that is showing: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0
Whilst my agent is set to, and on the majority of requests states it is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 OPR/110.0.0.0 (Edition Yx 05)
The request which sends the wrong header that i saw (there are more):
GET
https://www.eclipse.org/eclipse.org-common/themes/solstice/public/javascript/vendor/cookieconsent/default.min.js
Status
200
VersionHTTP/2
Transferred14.26 kB (39.43 kB size)
Referrer Policystrict-origin-when-cross-origin
DNS ResolutionSystem
I saw a second one: GET https://openvsxorg.blob.core.windows.net/resources/stateful/runme/darwin-arm64/3.9.0/icon.gif
I came across this issue as my Youtube doesn't work with this enabled - and I could see some requests with my actual user agent being sent.
Everything else is as default except I have it set to show debug in console, but it doesn't seem to do that.
I'm not sure if any of that's helpful or if it's expected or what.
This extension doesn't seem to be effective against a certain websites such as "open-vsx.org. The only way to get this website to recognize the custom useragent is via the Developer Tools on Chrome. This is definitely not a solution nor a workaround that needs to be adopted since it only works on the tab you set it for (as apposed to all the open tabs) and for that session only.
The text was updated successfully, but these errors were encountered: