On 6/29/2016 at 10:26 AM, David E. Ross's prodigious digits fired off:
On 6/29/2016 12:07 AM, Mark B wrote:Chase Bank recently updated their websites, and now they won't allow access using SeaMonkey. They say "You need to upgrade your browser to access your accounts and statements. Download a new version of your favorite browser here: Internet Explorer > (download the latest version.) Firefox > (download the latest version) Chrome > (download the lastest version) Safari >"I have been using SM for years to access Chase. Not about to use another browser just to do it their way. Call Chase Online services (877) 260-2178 and file a complaint. The first person you talk to can't do anything, so ask to escalate the complaint. I told them it was their problem, and gave them the user agent string: (Help/About SM) User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40. If enough people complain, they might do something about it other than say "We don't support SM." To which the reply should be "I don't support you." Mark BergerFirst of all, I found that enabling "Adertise Firefox compatibility" does NOT always resolve such problems. That merely changes my user agent (UA) string to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 which indicates Firefox, the mere presence of SeaMonkey in the UA string causes the Web site to reject me. Part of the problem is that banks and the like are required by their outside auditors and by their government regulators to test the security of their Web sites for particular user configurations. Any attempt to access their sites with configurations that were not tested are rejected. That means that the way I normally browse the Web is unacceptable to certain financial Web sites. I normally have: Cookies allowed only for the requested Web site File cookies.sqlite marked read-only Popups blocked Images from other domains blocked Flash installed but disabled Secret Agent extension confounding tracking Because of that, I created a separate SeaMonkey profile that I use only to access one bank, two credit unions, a mutual fund group, and a credit card issuer. This profile reverses those settings. Occasionally, one of those financial institutions updates their servers and still blocks me because of my UA string. When that happens, I enable "Advertise Firefox compatibility" in that profile. If that does not help, I use the PrefBar extension's User Agent menulist to change my UA string for that one institution. In any case, I also write a postal letter to the institution's board of directors to repeat "Gecko is Gecko". After a few weeks, SeaMonkey is accepted without enabling "Advertise Firefox compatibility". I think I started using this separate profile at least 8 years ago.
Interesting. Bank of America reacts to SeaMonkey by putting a notice at the top of the page:
"Our site may not work properly for the browser you're using. See recommended browsers"
I simply close the message and proceed normally. -- Ed Mullen http://edmullen.net/ We have enough youth. How about a fountain of smart? _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
