0
Forgive me if this is the wrong site to ask this question; some similar questions were closed on Web Applications Stack Exchange, so I asked this question here. If necessary, feel free to migrate this question.
Many current browsers identify themselves with user agent strings containing Mozilla/5.0
or Gecko
(as in like Gecko
), which only make sense for Firefox (and later versions of Netscape Navigator).
Why is this still being used? If, say, Chrome (the latest version as of this writing, on Windows 8.1 64-bit) identified itself as
Chrome/32.0.1700.107 (Windows NT 6.3; WOW64) AppleWebKit/537.36
instead of
Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36
would some websites not work correctly on it? Are there still web applications that rely on these substrings in the user agent string?
For reference, the user agent string for Firefox 27 on Windows 8.1 64-bit is:
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0
1I'd bet it's just legacy code; and I'd also bet that there are plenty of websites still using it, even though the common wisdom for a decade has been "don't sniff user agent strings!" – miken32 – 2014-02-12T20:58:55.660