• Rentlar@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    As useful as Mozilla/5.0; AppleWebKit/537.36 (KHTML, like Gecko) Safari/537.3

    • MonkderDritte@feddit.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      Mine is Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0. Joke is, this is the trimmed version (about:config xorigin and trimming settings) and some pages already have problems with it. If you strip out the OS, pages like google.com won’t work anymore. Despite that you shouldn’t parse the UA string…

      • Rentlar@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Trick is I took out the actually useful parts like Chrome, Firefox, Edge, etc. And the OS. All the agents these days have AppleWebKit and Mozilla just so old websites that look for it don’t downgrade the experience.

        • barsoap@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Firefox doesn’t pretend to use AppleWebKit. It’s actually the only one which identifies itself correctly… mostly, at least:

          Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0

          While about:support says “Window Protocol: wayland”. But that’s ok websites shouldn’t care anyway.

          It’s other browsers who send things like “like Gecko” to sneak past old browser-detection code.

        • 7heo@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          1 year ago

          Yeah, make your user agent absolutely unique. Too much entropy will surely confuse the shit out server side HTTP Header tracking. 😬