When SamsungBrowser on an Android tablet is configured to "Prefer desktop website" it sends the following user agent which resembles desktop Chrome on desktop Linux/X11.
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/28.0 Chrome/130.0.0.0 Safari/537.36
Is-Mobile: Yes, user-agent contains Samsung.
However, we classify it as mobile because of the samsung token in the mobile_redirect regex in the Varnish configuration.
I suspect this originates from 2009/2010, when we first wrote these regexes, to match various obscure user agent strings on Samsung phones. This likely also involved an uncommon browser engine (i.e. not Chrome-based and if it used WebKit, it was probably not using a UA string based on Safari but its own custom one).
Nowadays, the "Android" claim and/or the "Mobile" token (Chrome Mobile, Mobile Safari) are standard and widespread in all browser engines which should suffice.
Let's figure out why this is here and then decide on a path forward. Maybe we don't remove it but limit it first to avoid false positives e.g. match generic "Samsung" except for "SamsungBrowser" (the modern app based on Chromium).