On 3/31/18, WaltS48 <[email protected]> wrote: > On 3/30/18 10:25 PM, cmcadams wrote: >> Ed Mullen wrote: >>> On 3/30/2018 at 10:45 AM, Marisa Ciceran created this epitome of >>> digital genius: >>>> As of about a week ago, when I log into my Chase accounts account >>>> using SM 2.49.2 on my Windows 7 desktop and laptops, it goes to the >>>> following page: >>>> >>>> https://m.chase.com/secure.html?newstoken=false&Referer=https%3A%2F%2Fm.chase.com%2Findex.html&resId=success&#offerdetails >>>> >>>> >>>> >>>> The page is blank except for two options that run across the >>>> horizontal span of the page: 1) No thanks and 2) Call to apply. >>>> >>>> Neither of these buttons links to another page. However, that window >>>> still triggers the "time out" function that logs me out for >>>> non-activity. After that, I have the option to log back into MOBILE >>>> services. >>>> >>>> I've tried to report this issue to Chase customer support several >>>> times, but they refuse to file a report on the problem. Their only >>>> answer is that Seamonkey is not a supported browser, period. The >>>> fact that I am still recognized as being logged in is more than >>>> worrisome. >>>> >>>> I am not about to give up on Seamonkey which I have been using >>>> (under its prior names) for more than 20 years and which is still >>>> the best browser-mail suite on the internet. Any suggestions? >>>> >>>> Thanks. >>>> >>>> Marisa >>>> >>>> >>> >>> You simply need to use a different user agent string when going to >>> chase.com. Add this to your prefs.js: >>> >>> user_pref("general.useragent.override.chase.com", "Mozilla/5.0 >>> (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0"); >> >> Since I have a new Chase card I figured I should fix this sooner >> rather than later. >> >> Trying a user.js didn't work. >> >> prefs.js didn't wish to be changed...tried both Windows 7 Notepad and >> DOS Edit, but evidently didn't know the right save options, because >> after running SM the new entry disappeared. Rejected by SM, I suppose. >> >> Cutting to the chase (pun serendipitous): Creating a new entry in >> about:config by manually copying/pasting strings from Ed Mullen's >> example did work. >> >> To create a new entry in about:config you right-click on any entry and >> tell it you want a new string entry. Give it the name >> "general.useragent.override.chase.com" and the value "Mozilla/5.0 >> (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0". >> >> > > Why not ""Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) > Gecko/20100101 Firefox/59.0"? Which is the current version of Firefox.
Because SeaMonkey 2.49.2 is based on Firefox ESR 52 (extended support release?), so you've got a better chance of things working correctly if you pretend to have the latest version of Firefox ESR. & if Chase had competent web developers this wouldn't be an issue in the first place, but it is so you probably should have the rv:XXX number match the Firefox/XXX number: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Lee _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
