Re:Chrome phasing out support for User-Agent
by ksec on Wednesday March 25, 2020 @07:22PM
(#22689373)
I am guessing Banks only test their site against popular OS and Browser for security reasons.
[ Parent
| on HN ]
Re:Chrome phasing out support for User-Agent
by whoisthemachine on Wednesday March 25, 2020 @11:04PM
(#22690479)
It's usually just that the company doesn't want to have to deal with potential support calls that come in about their website not working on x os in x browser, so they do the bare minimum to disable it - then if a user complains about it not working, they can plausibly deny supporting the os/browser configuration.
Re:Chrome phasing out support for User-Agent
by asveikau on Wednesday March 25, 2020 @11:15PM
(#22690528)
This takes more effort than letting it just work. People running an OS more obscure than Linux are not the type that are going to call asking for support. We are used to supporting ourselves.
Did I mention it's the same code as a working configuration?
I think it's more likely somebody did not know how to properly parse user-agent and they blocked more than they intended to.
Re:Chrome phasing out support for User-Agent
by asveikau on Wednesday March 25, 2020 @08:18PM
(#22689759)
Ok then, don't tell all the other financial institutions I use FreeBSD then, they are all letting me through without issue.
It sounds a lot like you are making excuses for them and bad/lazy/poorly thought out code.
Re:Chrome phasing out support for User-Agent
by Dylan16807 on Wednesday March 25, 2020 @08:15PM
(#22689744)
I think you mean their broken idea of what a security reason is. Banks are generally really bad at actual web and mobile security.