Bablosoft

BAS use a malformed User-Agent

Support
  • G

    @jonigood, error in the site and not in the BAS...

    J 1 Reply
    2
  • G

    @jonigood, Fingerprint + old user-agent = No error, test project > ua_test.xml

    019e6fc0-84a5-4a42-92ab-c52c0963c126-image.png

    J 3 Replies
    0
  • J

    @GhostZ , yeh, only with a real chrome browser wee get a false positive on http://f.vision/ , however for firefox i get well :

    alt text

    still firefox from another machine:

    alt text

    And firefox from BAS :

    alt text

    What do you think about it ?
    thanks

    0
  • J

    @GhostZ said in BAS use a malformed User-Agent:

    old user-agent

    ok, interesting, i do some tests and I come back to you
    thanks

    0
  • J

    @GhostZ , how do you filtre old browser ?

    • Minimum added date
      I think it talks about the date of addition, no certainty about the version

    • Minimum browser version
      I can't find the inverse option, "Maximum browser version ?"

    thank you

    G 1 Reply
    0
  • G

    @jonigood, download the project that I attached

    J 1 Reply
    0
  • J

    @GhostZ , yeh i just understand ....

    thank you ;)

    0
  • J

    @GhostZ , hi

    It is not at all a question of old user-agent, it is only about the user agent of edge which work (old or new is same), the user-agent which you put in your example is a user-agent of edg , for chrome and firefox NO one user-agent works, old or new, for proof here are some tests:

    firefox, verry old user-agent (do not work) :

    Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5

    chrome, verry old user-agent (do not work) :

    5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/1.0.154.53 Safari/525.19

    edge, verry old user-agent (WORK) :

    Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246

    edge, new user-agent (WORK) : :

    Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.19582

    in no case can we accuse f.vision of false positive for firefox result, because all the tests with real FIREFOX browser pass well, never pass with BAS and firefox UA

    conclusion, there is a problem of user-agent with BAS, it would be necessary to report the bug, thank you.

    G 1 Reply
    0
  • G

    @jonigood, what difference does if in a real browser chrome writes that a fake user-agent, while chrome is the most popular browser

    1
  • J

    This a non-evolving way of thinking, the subject of the discussion is oriented on the fact that BAS is an automation tool which should accurately replicate the characteristics of a real browser, we simply observe that one of the functions of BAS (user -agent) does not react as it should, it doesn't matter if f.vision gives a fake also with real Chrome, the fact that we have different results on all other browsers shows that something is not working as it should be, it is undeniable

    in a large scale production environment, having the ability to only one kind of user-agent is simply impossible.

    You can do a test with our dear friend google with Recaptcha API (recaptcha__en.js), which unfortunately gives a poor score to BAS whit any user-agent other than edge :

    https://recaptcha-demo.appspot.com/recaptcha-v3-request-scores.php

    Whit a real browser whit get 0.7

    Whit base wee get 0.1:

    alt text

    This low score surely does not come only because of a possible (or not...) problem of user-agent whit BAS, but it is certainly part of it ...

    the same test with BAS and an EDGE User-Agent we get a better score, 0.3 .... :

    alt text

    f.vision is therefore not false, only the User-Agent of edge which are not detect whit BAS for the moment ...

    thank you

    0