Open RigoLigoRLC opened 3 years ago
For login pages, it is possible to use different methods to detect the user browser. If for instance you are on Chrome and use FF user-agent, the website can simply detect it (even with a CSS feature detection). Since the UA does not match with your browser, the protection layer of the website does not allow you to pass. To me, the only workaround is to add this page to the exception list unless someone can find what else we can spoof.
https://github.com/ray-lothian/UserAgent-Switcher/blob/master/extension/firefox/common.js#L35
For login pages, it is possible to use different methods to detect the user browser. If for instance you are on Chrome and use FF user-agent, the website can simply detect it (even with a CSS feature detection). Since the UA does not match with your browser, the protection layer of the website does not allow you to pass. To me, the only workaround is to add this page to the exception list unless someone can find what else we can spoof.
https://github.com/ray-lothian/UserAgent-Switcher/blob/master/extension/firefox/common.js#L35
One question though is that I did not alter my UA with the plugin; I even tried setting and resetting it to make sure the UA isn't being affected by the plugin, how could the check still fail?
So the action button was grey on GitLab? Can you reproduce this issue?
Not yet. In most of the times a check is not required.
On Tue, May 4, 2021, 4:27 PM ray-lothian @.***> wrote:
So the action button was grey on GitLab? Can you reproduce this issue?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ray-lothian/UserAgent-Switcher/issues/121#issuecomment-831769513, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALYTVUS5XQINCETQIYCEKFLTL6VXHANCNFSM4Z6F4KBQ .
If you have any diagnostics that I can run when I encounter the problem again, please send them here. Thanks.
I was signing in my GitLab account yesterday and found out the browser checking page won't successfully redirect. After some addon disabling, I found that it is this one that made it fail to redirect.