Re: Chase Bank doesn't like SeaMonkey

[Marisa Ciceran]

Sorry folks, I gave the wrong URL and file name. The correct ones are:

https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/ 
and seamonkey-2.46.en-US.win64.installer.exe 



Marisa Ciceran wrote:
The instructions provided by J. Weaver Jr. did the trick for me and 
are worth repeating:


 * In a browser page address bar, type "about:config" (without the
   quotes).
 * Anywhere in the body of the page, right click, select "New" and
   "String".
 * At the "Enter the preference name" prompt, type
   "general.useragent.override.chase.com" (without the quotes).
 * At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0)
   Gecko/20100101 Firefox/43.0" (again, without the quotes).

However, it may also be of significance to note that before applying 
them I  installed Seamonkey 2.46 64-bit to replace the 2.40 32-bit 
version on my Windows 7 Pro system since last March. The URL given for 
the download came from J. Weaver Jr. Rainer Ullrich in another thread 
that he posted to today. It, too, is also worth repeating -


https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/?C=M;O=D
   (file name is seamonkey-2.46.it.win32.installer.exe).

Thank you both (and others) for your constructive help!

Marisa


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Marisa Ciceran]

The instructions provided by J. Weaver Jr. did the trick for me and are 
worth repeating:


 * In a browser page address bar, type "about:config" (without the
   quotes).
 * Anywhere in the body of the page, right click, select "New" and
   "String".
 * At the "Enter the preference name" prompt, type
   "general.useragent.override.chase.com" (without the quotes).
 * At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0)
   Gecko/20100101 Firefox/43.0" (again, without the quotes).

However, it may also be of significance to note that before applying 
them I  installed Seamonkey 2.46 64-bit to replace the 2.40 32-bit 
version on my Windows 7 Pro system since last March. The URL given for 
the download came from J. Weaver Jr. Rainer Ullrich in another thread 
that he posted to today. It, too, is also worth repeating -


   
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/?C=M;O=D
   (file name is seamonkey-2.46.it.win32.installer.exe).

Thank you both (and others) for your constructive help!

Marisa


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 10/29/2016 7:39 PM, JAS wrote:
> J. Weaver Jr. wrote:
> 
>>
>> In a browser page address bar, type "about:config" (without the quotes).
>>
>> Anywhere in the body of the page, right click, select "New" and "String".
>>
>> At the "Enter the preference name" prompt, type
>> "general.useragent.override.chase.com" (without the quotes).
>>
>> At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0)
>> Gecko/20100101 Firefox/43.0" (again, without the quotes).
>>
>> Many other user agent strings will also work, but that one's working for
>> me.  -JW
> I thought that the general.useragent.override did not work anymore? At 
> least it does not for me.
> 

When I use the PrefBar extension to spoof a different browser, the
preference variable general.useragent.override -- the same one you cite
-- is what gets set.  I tested it at two Web pages, and it does work.

The two test pages are:

*  My own .  You can
see your own UA string under the entry for "UA".  Note that two UA
strings are shown there: my default UA string back in 2014 (when I last
updated the page) and any visitor's current UA string.

*  Panopticlick at .  After Panopticlick
did its analysis, I had to ask it for details.  The UA string appeared
near the bottom of the list of details.

If you manually edit prefs.js while SeaMonkey is an active application
(even if it is idle) rather than using about:config, it will not be
effective.  The prefs.js file on disc is read when SeaMonkey is
launched.  Thereafter, only the in-memory copy is used.  Furthermore,
the in-memory copy is then written over the disc file when SeaMonkey is
terminated.  In other words, DO NOT MANUALLY EDIT prefs.js.  (There is
an exception when moving the location of a SeaMonkey profile, either to
a different disc location or to a different computer.)

My preferred methods of changing preferences are, from most to least
preferred:
*  [Edit > Preferences] on the SeaMonkey menu bar
*  An extension, especially PrefBar
*  editing the file user.js, which requires SeaMonkey to be terminated
and then re-launched to become effective
*  about:config (generally only for testing a preference change)

The above is based on my experience with a major computer system used by
the U.S. military to operate its space satellites.  Part of my task was
to train U.S. Air Force officers on how to use the system.  I always
emphasized that changes to system controls were best done by using the
available user-oriented applications for that purpose instead of trying
to tweak the controls via the database system.  That ensured all
subsidiary changes related to the primary change -- many of which were
not obvious -- were also done because they were built into the
user-oriented applications.

The last time I edited the prefs.js file was in 2013, when my Windows XP
PC died and I had to rehost SeaMonkey on a Windows 7 PC.  Fortunately,
the hard drive containing my data (including my SeaMonkey profiles)
could be read by the new PC.

-- 
David E. Ross

Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[JAS]

JAS wrote:

J. Weaver Jr. wrote:



In a browser page address bar, type "about:config" (without the quotes).

Anywhere in the body of the page, right click, select "New" and "String".

At the "Enter the preference name" prompt, type
"general.useragent.override.chase.com" (without the quotes).

At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0)
Gecko/20100101 Firefox/43.0" (again, without the quotes).

Many other user agent strings will also work, but that one's working for
me.  -JW

I thought that the general.useragent.override did not work anymore? At
least it does not for me.

Nix my last reply as it does work and I had misspelled the word 
override. My bad.


--
   You either teach people to treat you with dignity and respect, or 
you don't. This means you are partly responsible for the mistreatment 
that you get at the hands of someone else.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[JAS]

J. Weaver Jr. wrote:



In a browser page address bar, type "about:config" (without the quotes).

Anywhere in the body of the page, right click, select "New" and "String".

At the "Enter the preference name" prompt, type
"general.useragent.override.chase.com" (without the quotes).

At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0)
Gecko/20100101 Firefox/43.0" (again, without the quotes).

Many other user agent strings will also work, but that one's working for
me.  -JW
I thought that the general.useragent.override did not work anymore? At 
least it does not for me.


--
   You either teach people to treat you with dignity and respect, or 
you don't. This means you are partly responsible for the mistreatment 
that you get at the hands of someone else.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Felix Miata]

NFN Smith composed on 2016-10-29 10:17 (UTC-0700):


Felix Miata wrote:



...automate...



...user.js...


only
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 10/29/2016 8:58 AM, Felix Miata wrote:
> NFN Smith composed on 2016-10-29 08:41 (UTC-0700):
> 
>> Thus, your choices for that are either hard-coding into prefs.js (which
>> you'll need to remove when you upgrade Seamonkey), or using one of the
>> extensions noted here.
> 
>> However, when you resort to spoofing you do have do a little maintenance
>> work, because Firefox versions are a constantly moving target. If you
>> hard-code into prefs.js, then you'll probably want to remove that
>> setting, when the next version of Seamonkey is released.
> 
> One should only ever manipulate prefs.js manually in the most extreme of 
> circumstances, and only with knowledge of the consequences. The right way to 
> automate inclusion of a prefs override is via user.js, a purely optional 
> profile file that SM will only read from, never write to.
> 
> http://kb.mozillazine.org/User.js_file
> 

Another reason to use user.js is that comments can be inserted into the
file to remind the user why a preference change has been inserted.
Other than the standard comment -- warning users not to manually edit
prefs.js -- comments cannot exist in prefs.js.

-- 
David E. Ross

Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[NFN Smith]

Felix Miata wrote:


One should only ever manipulate prefs.js manually in the most extreme of
circumstances, and only with knowledge of the consequences. The right
way to automate inclusion of a prefs override is via user.js, a purely
optional profile file that SM will only read from, never write to.

http://kb.mozillazine.org/User.js_file



Right.  Either user.js, or adding the necessary preference via about:config.

Smith

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Felix Miata]

NFN Smith composed on 2016-10-29 08:41 (UTC-0700):


Thus, your choices for that are either hard-coding into prefs.js (which
you'll need to remove when you upgrade Seamonkey), or using one of the
extensions noted here.



However, when you resort to spoofing you do have do a little maintenance
work, because Firefox versions are a constantly moving target. If you
hard-code into prefs.js, then you'll probably want to remove that
setting, when the next version of Seamonkey is released.


One should only ever manipulate prefs.js manually in the most extreme of 
circumstances, and only with knowledge of the consequences. The right way to 
automate inclusion of a prefs override is via user.js, a purely optional 
profile file that SM will only read from, never write to.


http://kb.mozillazine.org/User.js_file
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[NFN Smith]

Marisa Ciceran wrote:

I have been a faithful user of Seamonkey and its predecessors since the
mid-1990s. Have there been no updates to Seamonkey since the release of
version 2.40 in March 2016?



That's correct.


It is for months that I have been unable to log into my Chase bank
accounts because chase.com claims that Seamonkey is out of date.  I know
that there have been extensive discussions on this chronic problem, but
since I am not a programmer I have not been able to decipher from the
various threads whether or not a viable solution has been found. The
suggestions to change banks or stop using Seamonkey are not reasonable
options to me.


Or, another option would be to use another browser just for Chase. 
There's nothing that requires you to commit exclusively to a single browser.


However, judging by reports in this newsgroup, there seems to be an 
increasing number of sites that are complaining about Seamonkey. If you 
have the setting for Firefox compatibility enabled (and I don't remember 
where it is, at the moment), Seamonkey 2.40 advertises that it's Firefox 
43.0. Although Chase has had historic problems with demanding Firefox 
(and ignoring other Gecko browsers), I think the complaints are more 
from sites that object to Firefox 43, rather than Seamonkey.


Back in July, I did some testing with Seamonkey and Chase, and noting my 
results in a couple of messages that I posted to a similar discussion in 
this newsgroup.


I'll re-iterate highlights here:




I ran a some tests at https://chaseonline.chase.com, using both spoofing from 
PrefBar, as well as installed browsers. I found:

1) If I try a login with a standard Seamonkey Profile (and default user agent 
strings), Chase complains about my browser. UA string that I used is: 
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 
SeaMonkey/2.40

2) Using PrefBar to spoof, I have no problem logging in, if the UA is showing:

* default Firefox:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0

* Chrome:

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/49.0.2623.87 Safari/537.36

* Opera

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/49.0.2623.75 Safari/537.36 OPR/36.0.2130.32


3) I also found that when I am spoofing, after I get past the login dialog, I 
can change the UA back to the Seamonkey default, and there's no apparent 
problems with further access.

4) I tried a login with PaleMoon 32,, and found no problems with login.

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/49.0.2623.87 Safari/537.36



I also noted in a separate reply:




How does one go about changing the user agent string in SM2.40?
Could not easily find that information.


There's a couple of ways, as noted elsewhere in this thread.

1) You can do it permanently, via changes in prefs.js:

J. Weaver Jr. noted:


"about:config",

create string "general.useragent.override.chase.com"

set it to your current useragent string _without_ the "SeaMonkey".
(mine is "Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101
Firefox/43.0")


2) Use an extension, either PrefBar or UserAgentSwitcher.
Personally, I prefer PrefBar, partially because it seems easier to use,

> and partly, because I like some of the other options offered, of
> getting to preferences quickly.


I do know that with PrefBar, the default strings offered are *very*
old, and you generally have to go in and edit to match something
reasonably current. I'm currently using:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0


Since that posting, I've updated my spoofing string to use:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0


I suspect that when Seamonkey 2.46 comes out and the string used by 
advertising "Firefox compatibility" is upgraded, the growing number of 
Seamonkey conflicts will go away.  Until then, you'll have to do the 
compatibility settings yourself, to make sure you're advertising a more 
current version of Firefox.


Thus, your choices for that are either hard-coding into prefs.js (which 
you'll need to remove when you upgrade Seamonkey), or using one of the 
extensions noted here.


However, when you resort to spoofing you do have do a little maintenance 
work, because Firefox versions are a constantly moving target. If you 
hard-code into prefs.js, then you'll probably want to remove that 
setting, when the next version of Seamonkey is released.


Smith


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[WaltS48]

On 10/29/2016 11:20 AM, David E. Ross wrote:

On 10/29/2016 5:11 AM, Marisa Ciceran wrote:

I have been a faithful user of Seamonkey and its predecessors since the
mid-1990s. Have there been no updates to Seamonkey since the release of
version 2.40 in March 2016?

It is for months that I have been unable to log into my Chase bank
accounts because chase.com claims that Seamonkey is out of date.  I know
that there have been extensive discussions on this chronic problem, but
since I am not a programmer I have not been able to decipher from the
various threads whether or not a viable solution has been found. The
suggestions to change banks or stop using Seamonkey are not reasonable
options to me.

Can anyone please give this and other non-techie users a clue on the
status of this issue? I would appreciate it.

Thank you.

Marisa



I much prefer waiting for new versions than the every-6-weeks new
versions pushed for Firefox.

As for Chase Bank, the problem is with the bank and not SeaMonkey.
Chase's Web server simply rejects SeaMonkey.  However, you can always
have SeaMonkey make Web servers think you are using Firefox.  Several
suggestions on how to do this have already been made in this discussion.
  Also previously suggested is that you change to a bank that does not
discriminate against SeaMonkey.




Well, SeaMonkey is supposed to follow the Firefox release schedule, but 
they keep having problems getting them to build.



--
Visit Pittsburgh 
Coexist 
National Popular Vote 
Ubuntu 16.04LTS
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 10/29/2016 5:11 AM, Marisa Ciceran wrote:
> I have been a faithful user of Seamonkey and its predecessors since the 
> mid-1990s. Have there been no updates to Seamonkey since the release of 
> version 2.40 in March 2016?
> 
> It is for months that I have been unable to log into my Chase bank 
> accounts because chase.com claims that Seamonkey is out of date.  I know 
> that there have been extensive discussions on this chronic problem, but 
> since I am not a programmer I have not been able to decipher from the 
> various threads whether or not a viable solution has been found. The 
> suggestions to change banks or stop using Seamonkey are not reasonable 
> options to me.
> 
> Can anyone please give this and other non-techie users a clue on the 
> status of this issue? I would appreciate it.
> 
> Thank you.
> 
> Marisa
> 

I much prefer waiting for new versions than the every-6-weeks new
versions pushed for Firefox.

As for Chase Bank, the problem is with the bank and not SeaMonkey.
Chase's Web server simply rejects SeaMonkey.  However, you can always
have SeaMonkey make Web servers think you are using Firefox.  Several
suggestions on how to do this have already been made in this discussion.
 Also previously suggested is that you change to a bank that does not
discriminate against SeaMonkey.

-- 
David E. Ross

Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[J. Weaver Jr.]

Marisa Ciceran wrote:

I have been a faithful user of Seamonkey and its predecessors since the
mid-1990s. Have there been no updates to Seamonkey since the release of
version 2.40 in March 2016?

It is for months that I have been unable to log into my Chase bank
accounts because chase.com claims that Seamonkey is out of date.  I know
that there have been extensive discussions on this chronic problem, but
since I am not a programmer I have not been able to decipher from the
various threads whether or not a viable solution has been found. The
suggestions to change banks or stop using Seamonkey are not reasonable
options to me.

Can anyone please give this and other non-techie users a clue on the
status of this issue? I would appreciate it.


In a browser page address bar, type "about:config" (without the quotes).

Anywhere in the body of the page, right click, select "New" and "String".

At the "Enter the preference name" prompt, type 
"general.useragent.override.chase.com" (without the quotes).


At the next prompt, type "Mozilla/5.0 (Windows NT 6.1; rv:43.0) 
Gecko/20100101 Firefox/43.0" (again, without the quotes).


Many other user agent strings will also work, but that one's working for 
me.  -JW

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Marisa Ciceran]

I have been a faithful user of Seamonkey and its predecessors since the 
mid-1990s. Have there been no updates to Seamonkey since the release of 
version 2.40 in March 2016?


It is for months that I have been unable to log into my Chase bank 
accounts because chase.com claims that Seamonkey is out of date.  I know 
that there have been extensive discussions on this chronic problem, but 
since I am not a programmer I have not been able to decipher from the 
various threads whether or not a viable solution has been found. The 
suggestions to change banks or stop using Seamonkey are not reasonable 
options to me.


Can anyone please give this and other non-techie users a clue on the 
status of this issue? I would appreciate it.


Thank you.

Marisa

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Richard Owlett]

On 10/25/2016 8:12 AM, Rick Merrill wrote:


Some of the TOOLS for webpages only support certain browsers, but
not standards.  There should be an underwriters' lab for web
pages ;-)


Actually there is.
"The World Wide Web Consortium (W3C) is an international 
community where
 Member organizations, a full-time staff, and the public work 
together to

 develop Web standards." https://www.w3.org/Consortium/

Their test suite is available at http://validator.w3.org/ .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Rick Merrill]

On 9/7/2016 10:41 AM, Ray_Net wrote:

Ed Mullen wrote on 07/09/2016 16:15:

On 9/7/2016 at 7:31 AM, Daniel's prodigious digits fired off:

On 7/09/2016 5:15 AM, Ray_Net wrote:

David E. Ross wrote on 05/09/2016 22:38:

On 9/5/2016 12:17 PM, Ray_Net wrote:

Jerry wrote on 04/09/2016 15:12:

I've been following this thread with much interest, since I had the
same problem with CHASE. I am happy to report that as of today I can
now log into my Chase account with Seamonkey 2.45 on Linux.

I have the User Agent Switcher addon installed. In that I entered a
new User Agent I named Seamonkey. For the User Agent string I have
"Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0". I removed Seamonkey from the end of the string
(taking
the clue from David's last post), and now it works!

Oh, I did go in and delete all chase.com cookies before I tried
to log
in to Chase.

Thanks to all of you for not giving up and sorting this out!





As I said before .. SM must ONLY have Firefox in his User Agent
String ...
... when "Advertise Firefox compatibility" is checked.


No, that would indicate Firefox is the browser.  "Advertise Firefox
compatibility" should indicate both SeaMonkey and Firefox.

Actually, when I use PrefBar's user agent spoofing, my user agent
strings is
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40, NOT Firefox/45.0

If I were to enable "Advertise Firefox compatibility", the string
would be
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Many cases of user agent sniffing merely look for "Firefox" without
considering the rest of the string.  It would be better to look for
"Gecko", in which case all this discussion would be moot. Of course,
that would have to change when Gecko is abandoned in favor of
Servo; but
that replacement is not yet certain.


I just think that if SM say that It is Firefox ... NO problems when
webmasters does bad sniffing.
It's more sites than "a few" .
Most of WebMasters ignore SeaMonkey ... saying : what's that ?
And don't care about "gecko" which is not a browser ...


And as long as they don't know about SeaMonkey or any of the other
browsers that are based on Gecko, the "WebMasters" will never know about
SeaMonkey or any of the other browsers that are based on Gecko!!

I don't think anyone here is suggesting that *you have to*, but then
don't complain when your SeaMonkey Browser that is advertising itself as
Firefox doesn't work as you would expect it to.



The problem is that Web site designers are doing non-standard things
and shouldn't be.  If they'd design standards-compliant pages there'd
be no need for sniffing.





That's correct. And in respond to "don't complain when your SeaMonkey
Browser that is advertising itself as
Firefox doesn't work as you would expect it to." I say: IF Firefox
render correctly the website SM will do the same.
In addition, you can speak about SeaMonkey to WebMasters ... they will
continue to ignore this Browser ... they don't care about the great list
of other Browsers that exist, they support.only their little list.


Some of the TOOLS for webpages only support certain browsers, but not 
standards.  There should be an underwriters' lab for web pages ;-)

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with Modified User.js

[Arnie Goetchius]

WaltS48 wrote:
> On 09/13/2016 09:03 PM, Arnie Goetchius wrote:
>> When I open SM using the profile for Default User, I get exactly what
>> you get. However, when I open SM using my regular profile, I can access
>> the Chase site with no problem. I modified the user.js file as suggested
>> by Dennis Ross and that lets me in without suggesting that my browser
>> needs to be upgraded.
> 
> 
> I'm not a Chase customer, but didn't one poster say it works with the
> default SeaMonkey UA, no modifications needed, or what? I'm so confused.
> :-\
> 
> Oh yeah, it's in the Subject line of this post.
> 
That was me and it was a mistake on my part. It only worked after I
modified user.js. I changed the Subject to reflect that a modified
user.js is required
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[WaltS48]

On 09/13/2016 09:03 PM, Arnie Goetchius wrote:

When I open SM using the profile for Default User, I get exactly what
you get. However, when I open SM using my regular profile, I can access
the Chase site with no problem. I modified the user.js file as suggested
by Dennis Ross and that lets me in without suggesting that my browser
needs to be upgraded.



I'm not a Chase customer, but didn't one poster say it works with the 
default SeaMonkey UA, no modifications needed, or what? I'm so confused. :-\


Oh yeah, it's in the Subject line of this post.

--

Visit Pittsburgh 
Ubuntu 16.04.1 LTS

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Arnie Goetchius]

Lemuel Johnson wrote:
> On 9/13/2016 4:25 PM, Arnie Goetchius wrote:
>> Lemuel Johnson wrote:
>>> On 9/13/2016 9:48 AM, Ed Mullen wrote:
 On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off:
> On 9/12/2016 12:04 PM, Ed Mullen wrote:
>> On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired
>> off:
>>> On 9/11/2016 8:19 PM, Ed Mullen wrote:
 On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired
 off:
> On 9/10/2016 12:28 PM, Ed Mullen wrote:
>> On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits
>> fired
>> off:
>>> On 9/2/2016 1:56 PM, Arnie Goetchius wrote:
 snipped<
 As of today, I can now log into the Chase website with the
 default
 User
 Agent for Seamonkey. This is what my UA shows:

 Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
 Firefox/43.0 SeaMonkey/2.40

>>>
>>> Chase is still not allowing me access.
>>>
>>> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
>>> Firefox/43.0
>>> SeaMonkey/2.40
>>>
>>> I also tried spoofing "Windows NT 10.0" without success.
>>
>> Try clearing out any Chase cookies and make sure you allow them.
>>
>
> Did that first, also cleared cache.  Still no go:
> "You need to upgrade your browser to access your accounts and
> statements."

 Change banks.


>>>
>>> I appreciate the suggestions.  But as a SeaMonkey proponent, maybe
>>> even
>>> evangelist, I have convinced several friends and family members
>>> to use
>>> SM as their browser and email client.  They also have Chase
>>> accounts.
>>>
>>> The reality is:
>>> 1. They are not changing banks.
>>> 2. They have no idea what a User Agent is or any desire to learn.
>>> 3. They will not use a different browser just to access chase.com
>>> 4. If they move to a different browser they will not be using
>>> SeaMonkey
>>> again.
>>>
>>> So, there was a report that chase.com was usable with the default
>>> SeaMonkey user agent.  That would be good, but I cannot
>>> replicate.  My
>>> question is more along the lines of "Am I doing something wrong that
>>> prevents (default) SeaMonkey from being accepted at chase.com?"
>>
>> Okay, so exactly what is happening when you try to log in?  What
>> message
>> does the site give you?
>>
>> I just went there and tried to log in with fake info and the site
>> dutifully directed me to an error page.
>>
>>
>
> After a successful login, I am re-directed to
> https://www.chase.com/services/browser-upgrade,
>
> where the first sentence is:
> "You need to upgrade your browser to access your accounts and
> statements."
>
> Then they provide links to Internet Explorer, Firefox, Chrome and
> Safari.

 I'm confused.  You can log in. When redirected to that page can you
 navigate into your account info? Or do they prevent that?

>>>
>>> After login I can only access that page. Bookmarked links to other
>>> internal pages all redirect to the "browser-upgrade" page.  Browser
>>> sniffing is bad, but they do it well.
>> By login, do you mean you actually signed in with your userid and
>> password or do mean you opened the page at www.chase.com?
>>
> 
> Username and password...
When I open SM using the profile for Default User, I get exactly what
you get. However, when I open SM using my regular profile, I can access
the Chase site with no problem. I modified the user.js file as suggested
by Dennis Ross and that lets me in without suggesting that my browser
needs to be upgraded.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/13/2016 4:25 PM, Arnie Goetchius wrote:

Lemuel Johnson wrote:

On 9/13/2016 9:48 AM, Ed Mullen wrote:

On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off:

On 9/12/2016 12:04 PM, Ed Mullen wrote:

On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off:

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired
off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired
off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the
default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe
even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using
SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"


Okay, so exactly what is happening when you try to log in?  What
message
does the site give you?

I just went there and tried to log in with fake info and the site
dutifully directed me to an error page.




After a successful login, I am re-directed to
https://www.chase.com/services/browser-upgrade,

where the first sentence is:
"You need to upgrade your browser to access your accounts and
statements."

Then they provide links to Internet Explorer, Firefox, Chrome and
Safari.


I'm confused.  You can log in. When redirected to that page can you
navigate into your account info? Or do they prevent that?



After login I can only access that page. Bookmarked links to other
internal pages all redirect to the "browser-upgrade" page.  Browser
sniffing is bad, but they do it well.

By login, do you mean you actually signed in with your userid and
password or do mean you opened the page at www.chase.com?



Username and password...
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Arnie Goetchius]

Lemuel Johnson wrote:
> On 9/13/2016 9:48 AM, Ed Mullen wrote:
>> On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off:
>>> On 9/12/2016 12:04 PM, Ed Mullen wrote:
 On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off:
> On 9/11/2016 8:19 PM, Ed Mullen wrote:
>> On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired
>> off:
>>> On 9/10/2016 12:28 PM, Ed Mullen wrote:
 On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired
 off:
> On 9/2/2016 1:56 PM, Arnie Goetchius wrote:
>> snipped<
>> As of today, I can now log into the Chase website with the
>> default
>> User
>> Agent for Seamonkey. This is what my UA shows:
>>
>> Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>> Firefox/43.0 SeaMonkey/2.40
>>
>
> Chase is still not allowing me access.
>
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
> Firefox/43.0
> SeaMonkey/2.40
>
> I also tried spoofing "Windows NT 10.0" without success.

 Try clearing out any Chase cookies and make sure you allow them.

>>>
>>> Did that first, also cleared cache.  Still no go:
>>> "You need to upgrade your browser to access your accounts and
>>> statements."
>>
>> Change banks.
>>
>>
>
> I appreciate the suggestions.  But as a SeaMonkey proponent, maybe
> even
> evangelist, I have convinced several friends and family members to use
> SM as their browser and email client.  They also have Chase accounts.
>
> The reality is:
> 1. They are not changing banks.
> 2. They have no idea what a User Agent is or any desire to learn.
> 3. They will not use a different browser just to access chase.com
> 4. If they move to a different browser they will not be using
> SeaMonkey
> again.
>
> So, there was a report that chase.com was usable with the default
> SeaMonkey user agent.  That would be good, but I cannot replicate.  My
> question is more along the lines of "Am I doing something wrong that
> prevents (default) SeaMonkey from being accepted at chase.com?"

 Okay, so exactly what is happening when you try to log in?  What
 message
 does the site give you?

 I just went there and tried to log in with fake info and the site
 dutifully directed me to an error page.


>>>
>>> After a successful login, I am re-directed to
>>> https://www.chase.com/services/browser-upgrade,
>>>
>>> where the first sentence is:
>>> "You need to upgrade your browser to access your accounts and
>>> statements."
>>>
>>> Then they provide links to Internet Explorer, Firefox, Chrome and
>>> Safari.
>>
>> I'm confused.  You can log in. When redirected to that page can you
>> navigate into your account info? Or do they prevent that?
>>
> 
> After login I can only access that page. Bookmarked links to other
> internal pages all redirect to the "browser-upgrade" page.  Browser
> sniffing is bad, but they do it well.
By login, do you mean you actually signed in with your userid and
password or do mean you opened the page at www.chase.com?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/13/2016 9:48 AM, Ed Mullen wrote:

On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off:

On 9/12/2016 12:04 PM, Ed Mullen wrote:

On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off:

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired
off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"


Okay, so exactly what is happening when you try to log in?  What message
does the site give you?

I just went there and tried to log in with fake info and the site
dutifully directed me to an error page.




After a successful login, I am re-directed to
https://www.chase.com/services/browser-upgrade,

where the first sentence is:
"You need to upgrade your browser to access your accounts and
statements."

Then they provide links to Internet Explorer, Firefox, Chrome and Safari.


I'm confused.  You can log in. When redirected to that page can you
navigate into your account info? Or do they prevent that?



After login I can only access that page. Bookmarked links to other 
internal pages all redirect to the "browser-upgrade" page.  Browser 
sniffing is bad, but they do it well.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ed Mullen]

On 9/12/2016 at 6:45 PM, Lemuel Johnson's prodigious digits fired off:

On 9/12/2016 12:04 PM, Ed Mullen wrote:

On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off:

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired
off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"


Okay, so exactly what is happening when you try to log in?  What message
does the site give you?

I just went there and tried to log in with fake info and the site
dutifully directed me to an error page.




After a successful login, I am re-directed to
https://www.chase.com/services/browser-upgrade,

where the first sentence is:
"You need to upgrade your browser to access your accounts and statements."

Then they provide links to Internet Explorer, Firefox, Chrome and Safari.


I'm confused.  You can log in. When redirected to that page can you 
navigate into your account info? Or do they prevent that?


--
Ed Mullen
http://edmullen.net/
If man evolved from apes why do we still have apes?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/12/2016 6:22 PM, Paul B. Gallagher wrote:
> David E. Ross wrote:
> 
>> On 9/12/2016 2:16 PM, Paul B. Gallagher wrote:
>>> But if cookies.sqlite is marked "read-only," how can a site set a
>>> cookie, even if it's an approved site? I mean, the definition of "set a
>>> cookie" includes "modify cookies.sqlite," does it not? Confusinger and
>>> confusinger...
>>>
>>> Do bank sites really work with stale cookies from previous visits?
>>> Sounds like a great way for hackers to impersonate you -- just spoof
>>> your cookie from a previous session.
>>
>> Two profiles, each with its own file named cookies.sqlite:
>>
>> (1)  Profile for general Web surfing --  The file cookies.sqlite is
>> marked "read only".  When a Web server sends a cookie along with the
>> HTML of a Web page, that cookie sits in the the browser's (SeaMonkey or
>> Firefox) memory.  It does not get written to the on-disc file until
>> either the memory space for cookies is filled or (more likely) the
>> browser is terminated.
> 
> Aha! I didn't realize SM could hold cookies in memory without writing 
> them to disk and still have them work.
> 
> I'm still not clear on how they can be written to a read-only file under 
> any conditions (e.g., "when the cookie memory space is filled or the 
> browser is terminated"). AFAIK, "read-only" means "read-only."
> 

That is correct.  For the "read only" cookies.sqlite file, cookies are
NOT written or even updated (although SeaMonkey might attempt a write
operation).  And when they expire, I have to change the file to
"read-write" and use the old Cookie Manager to delete them manually.

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Arnie Goetchius]

Lemuel Johnson wrote:
> On 9/12/2016 12:31 PM, David E. Ross wrote:
>> On 9/12/2016 9:24 AM, Lemuel Johnson wrote:
>>> snipped
>>>
>>> I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
>>> evangelist, I have convinced several friends and family members to use
>>> SM as their browser and email client.  They also have Chase accounts.
>>>
>>> The reality is:
>>> 1. They are not changing banks.
>>> 2. They have no idea what a User Agent is or any desire to learn.
>>> 3. They will not use a different browser just to access chase.com
>>> 4. If they move to a different browser they will not be using SeaMonkey
>>> again.
>>>
>>> So, there was a report that chase.com was usable with the default
>>> SeaMonkey user agent.  That would be good, but I cannot replicate.  My
>>> question is more along the lines of "Am I doing something wrong that
>>> prevents (default) SeaMonkey from being accepted at chase.com?"
>>>
>>
>> I had to create a separate SeaMonkey profile for accessing my financial
>> accounts at a bank, two credit unions, and Vanguard mutual funds.  My
>> settings for this profile might give you some idea of what you might
>> need to do.  Where I say "Normally", that reflects the profile where I
>> do most of my Web surfing.
>>
>> Images from all domains (Normally, I block images from "other" domains.)
>>
>> Cookies from 3rd party domains allowed from which there are already
>> existing cookies and the file cookies.sqlite is marked "read-write".
>> (Normally, I allow cookies only from the requested domain; and I mark
>> cookies.sqlite as "read only".)
>>
>> Popups enabled (Normally, I disable popups.)
>>
>> FlashBlock extension and HTML5 Media enabled  (Normally, they are
>> disabled.)
>>
>> AdBlock Plus and Secret Agent extensions not installed.  (They are
>> installed in the profile where I do most of my Web surfing.)
>>
> 
> Browser preferences at default settings:
> Load all images
> Allow all cookies (normally).  cookies.sqlite is RW
> Block unrequested popup windows checked (I believe this is default)
> None of these are installed: FlashBlock, HTML5 Media, AdBlock, Secret
> Agent.  This is such a blatant case of browser sniffing I doubt any
> extension would cause the problem.
> 
> 
> 
Per David Ross's post on 8/30. I added the following to prefs.js

user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");

It did not work right away so stopped playing with it. Someone suggested
that any chase cookies be deleted. After I did that, it started working
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Paul B. Gallagher]

David E. Ross wrote:


On 9/12/2016 2:16 PM, Paul B. Gallagher wrote:

But if cookies.sqlite is marked "read-only," how can a site set a
cookie, even if it's an approved site? I mean, the definition of "set a
cookie" includes "modify cookies.sqlite," does it not? Confusinger and
confusinger...

Do bank sites really work with stale cookies from previous visits?
Sounds like a great way for hackers to impersonate you -- just spoof
your cookie from a previous session.


Two profiles, each with its own file named cookies.sqlite:

(1)  Profile for general Web surfing --  The file cookies.sqlite is
marked "read only".  When a Web server sends a cookie along with the
HTML of a Web page, that cookie sits in the the browser's (SeaMonkey or
Firefox) memory.  It does not get written to the on-disc file until
either the memory space for cookies is filled or (more likely) the
browser is terminated.


Aha! I didn't realize SM could hold cookies in memory without writing 
them to disk and still have them work.


I'm still not clear on how they can be written to a read-only file under 
any conditions (e.g., "when the cookie memory space is filled or the 
browser is terminated"). AFAIK, "read-only" means "read-only."


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Arnie Goetchius]

Lemuel Johnson wrote:
> On 9/12/2016 12:31 PM, David E. Ross wrote:
>> On 9/12/2016 9:24 AM, Lemuel Johnson wrote:
>>> snipped
>>>
>>> I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
>>> evangelist, I have convinced several friends and family members to use
>>> SM as their browser and email client.  They also have Chase accounts.
>>>
>>> The reality is:
>>> 1. They are not changing banks.
>>> 2. They have no idea what a User Agent is or any desire to learn.
>>> 3. They will not use a different browser just to access chase.com
>>> 4. If they move to a different browser they will not be using SeaMonkey
>>> again.
>>>
>>> So, there was a report that chase.com was usable with the default
>>> SeaMonkey user agent.  That would be good, but I cannot replicate.  My
>>> question is more along the lines of "Am I doing something wrong that
>>> prevents (default) SeaMonkey from being accepted at chase.com?"

I created that report but have since found out that it was not as true
statement. When I use the "Default" profile, Chase is not usable. I did
change the prefs.js but I originally thought that the change made no
difference. However, I now think it did fix the Chase problem. I will go
back and research what I did and let you know. Sorry for the misinformation.
>>
>> I had to create a separate SeaMonkey profile for accessing my financial
>> accounts at a bank, two credit unions, and Vanguard mutual funds.  My
>> settings for this profile might give you some idea of what you might
>> need to do.  Where I say "Normally", that reflects the profile where I
>> do most of my Web surfing.
>>
>> Images from all domains (Normally, I block images from "other" domains.)
>>
>> Cookies from 3rd party domains allowed from which there are already
>> existing cookies and the file cookies.sqlite is marked "read-write".
>> (Normally, I allow cookies only from the requested domain; and I mark
>> cookies.sqlite as "read only".)
>>
>> Popups enabled (Normally, I disable popups.)
>>
>> FlashBlock extension and HTML5 Media enabled  (Normally, they are
>> disabled.)
>>
>> AdBlock Plus and Secret Agent extensions not installed.  (They are
>> installed in the profile where I do most of my Web surfing.)
>>
> 
> Browser preferences at default settings:
> Load all images
> Allow all cookies (normally).  cookies.sqlite is RW
> Block unrequested popup windows checked (I believe this is default)
> None of these are installed: FlashBlock, HTML5 Media, AdBlock, Secret
> Agent.  This is such a blatant case of browser sniffing I doubt any
> extension would cause the problem.
> 
> 
> 

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/12/2016 2:16 PM, Paul B. Gallagher wrote:
> David E. Ross wrote:
>> On 9/12/2016 10:37 AM, Paul B. Gallagher wrote:
>>> David E. Ross wrote:
>>>
 I had to create a separate SeaMonkey profile for accessing my
 financial accounts at a bank, two credit unions, and Vanguard mutual
 funds.  My settings for this profile might give you some idea of what
 you might need to do.  Where I say "Normally", that reflects the
 profile where I do most of my Web surfing.

 ...

 Cookies from 3rd party domains allowed from which there are already
 existing cookies and the file cookies.sqlite is marked "read-write".
 (Normally, I allow cookies only from the requested domain; and I
 mark cookies.sqlite as "read only".)
>>>
>>> I'm very curious about how you made this work. Under normal conditions,
>>> you accept first-party cookies but you prevent SM from updating the
>>> cookies file? How can both be true?
>>>
>>
>> I first set the preference to allow ALL cookies.  I then visited the Web
>> sites of the financial institutions.  After that, I changed the
>> preference to "Allow third-party cookies for previously visited websites
>> only".  In that profile, I always had cookies.sqlite marked
>> "read-write".  Only in the profile I use for most of my Web surfing, I
>> marked that file "read only".
> 
> But if cookies.sqlite is marked "read-only," how can a site set a 
> cookie, even if it's an approved site? I mean, the definition of "set a 
> cookie" includes "modify cookies.sqlite," does it not? Confusinger and 
> confusinger...
> 
> Do bank sites really work with stale cookies from previous visits? 
> Sounds like a great way for hackers to impersonate you -- just spoof 
> your cookie from a previous session.
> 

Two profiles, each with its own file named cookies.sqlite:

(1)  Profile for general Web surfing --  The file cookies.sqlite is
marked "read only".  When a Web server sends a cookie along with the
HTML of a Web page, that cookie sits in the the browser's (SeaMonkey or
Firefox) memory.  It does not get written to the on-disc file until
either the memory space for cookies is filled or (more likely) the
browser is terminated.

(2)  Profile for accessing financial accounts -- The file cookies.sqlite
is marked "read-write".

As for stale cookies, the cookies in profile #2 above are sent back to
the Web server when I request a Web page.  The server returns those
cookies with updated content.  The content might identify my browser and
PC.  If I blocked cookies in this profile, the Web server would require
me to go through several additional steps to login because the server
does not recognize my configuration as belonging to an authentic user.
The server might also not use my preferred settings for my account
because those settings are in my cookies.

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/12/2016 12:31 PM, David E. Ross wrote:

On 9/12/2016 9:24 AM, Lemuel Johnson wrote:

snipped

I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"



I had to create a separate SeaMonkey profile for accessing my financial
accounts at a bank, two credit unions, and Vanguard mutual funds.  My
settings for this profile might give you some idea of what you might
need to do.  Where I say "Normally", that reflects the profile where I
do most of my Web surfing.

Images from all domains (Normally, I block images from "other" domains.)

Cookies from 3rd party domains allowed from which there are already
existing cookies and the file cookies.sqlite is marked "read-write".
(Normally, I allow cookies only from the requested domain; and I mark
cookies.sqlite as "read only".)

Popups enabled (Normally, I disable popups.)

FlashBlock extension and HTML5 Media enabled  (Normally, they are
disabled.)

AdBlock Plus and Secret Agent extensions not installed.  (They are
installed in the profile where I do most of my Web surfing.)



Browser preferences at default settings:
Load all images
Allow all cookies (normally).  cookies.sqlite is RW
Block unrequested popup windows checked (I believe this is default)
None of these are installed: FlashBlock, HTML5 Media, AdBlock, Secret 
Agent.  This is such a blatant case of browser sniffing I doubt any 
extension would cause the problem.




___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/12/2016 12:04 PM, Ed Mullen wrote:

On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off:

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired
off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"


Okay, so exactly what is happening when you try to log in?  What message
does the site give you?

I just went there and tried to log in with fake info and the site
dutifully directed me to an error page.




After a successful login, I am re-directed to
https://www.chase.com/services/browser-upgrade,

where the first sentence is:
"You need to upgrade your browser to access your accounts and statements."

Then they provide links to Internet Explorer, Firefox, Chrome and Safari.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Paul B. Gallagher]

David E. Ross wrote:

On 9/12/2016 10:37 AM, Paul B. Gallagher wrote:

David E. Ross wrote:


I had to create a separate SeaMonkey profile for accessing my
financial accounts at a bank, two credit unions, and Vanguard mutual
funds.  My settings for this profile might give you some idea of what
you might need to do.  Where I say "Normally", that reflects the
profile where I do most of my Web surfing.

...

Cookies from 3rd party domains allowed from which there are already
existing cookies and the file cookies.sqlite is marked "read-write".
(Normally, I allow cookies only from the requested domain; and I
mark cookies.sqlite as "read only".)


I'm very curious about how you made this work. Under normal conditions,
you accept first-party cookies but you prevent SM from updating the
cookies file? How can both be true?



I first set the preference to allow ALL cookies.  I then visited the Web
sites of the financial institutions.  After that, I changed the
preference to "Allow third-party cookies for previously visited websites
only".  In that profile, I always had cookies.sqlite marked
"read-write".  Only in the profile I use for most of my Web surfing, I
marked that file "read only".


But if cookies.sqlite is marked "read-only," how can a site set a 
cookie, even if it's an approved site? I mean, the definition of "set a 
cookie" includes "modify cookies.sqlite," does it not? Confusinger and 
confusinger...


Do bank sites really work with stale cookies from previous visits? 
Sounds like a great way for hackers to impersonate you -- just spoof 
your cookie from a previous session.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/12/2016 10:37 AM, Paul B. Gallagher wrote:
> David E. Ross wrote:
> 
>> I had to create a separate SeaMonkey profile for accessing my
>> financial accounts at a bank, two credit unions, and Vanguard mutual
>> funds.  My settings for this profile might give you some idea of what
>> you might need to do.  Where I say "Normally", that reflects the
>> profile where I do most of my Web surfing.
>>
>> ...
>>
>> Cookies from 3rd party domains allowed from which there are already
>> existing cookies and the file cookies.sqlite is marked "read-write".
>> (Normally, I allow cookies only from the requested domain; and I
>> mark cookies.sqlite as "read only".)
> 
> I'm very curious about how you made this work. Under normal conditions, 
> you accept first-party cookies but you prevent SM from updating the 
> cookies file? How can both be true?
> 

I first set the preference to allow ALL cookies.  I then visited the Web
sites of the financial institutions.  After that, I changed the
preference to "Allow third-party cookies for previously visited websites
only".  In that profile, I always had cookies.sqlite marked
"read-write".  Only in the profile I use for most of my Web surfing, I
marked that file "read only".

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Paul B. Gallagher]

David E. Ross wrote:


I had to create a separate SeaMonkey profile for accessing my
financial accounts at a bank, two credit unions, and Vanguard mutual
funds.  My settings for this profile might give you some idea of what
you might need to do.  Where I say "Normally", that reflects the
profile where I do most of my Web surfing.

...

Cookies from 3rd party domains allowed from which there are already
existing cookies and the file cookies.sqlite is marked "read-write".
(Normally, I allow cookies only from the requested domain; and I
mark cookies.sqlite as "read only".)


I'm very curious about how you made this work. Under normal conditions, 
you accept first-party cookies but you prevent SM from updating the 
cookies file? How can both be true?


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/12/2016 9:24 AM, Lemuel Johnson wrote:
> On 9/11/2016 8:19 PM, Ed Mullen wrote:
>> On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:
>>> On 9/10/2016 12:28 PM, Ed Mullen wrote:
 On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:
> On 9/2/2016 1:56 PM, Arnie Goetchius wrote:
>> snipped<
>> As of today, I can now log into the Chase website with the default
>> User
>> Agent for Seamonkey. This is what my UA shows:
>>
>> Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>> Firefox/43.0 SeaMonkey/2.40
>>
>
> Chase is still not allowing me access.
>
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
> Firefox/43.0
> SeaMonkey/2.40
>
> I also tried spoofing "Windows NT 10.0" without success.

 Try clearing out any Chase cookies and make sure you allow them.

>>>
>>> Did that first, also cleared cache.  Still no go:
>>> "You need to upgrade your browser to access your accounts and
>>> statements."
>>
>> Change banks.
>>
>>
> 
> I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even 
> evangelist, I have convinced several friends and family members to use 
> SM as their browser and email client.  They also have Chase accounts.
> 
> The reality is:
> 1. They are not changing banks.
> 2. They have no idea what a User Agent is or any desire to learn.
> 3. They will not use a different browser just to access chase.com
> 4. If they move to a different browser they will not be using SeaMonkey 
> again.
> 
> So, there was a report that chase.com was usable with the default 
> SeaMonkey user agent.  That would be good, but I cannot replicate.  My 
> question is more along the lines of "Am I doing something wrong that 
> prevents (default) SeaMonkey from being accepted at chase.com?"
> 

I had to create a separate SeaMonkey profile for accessing my financial
accounts at a bank, two credit unions, and Vanguard mutual funds.  My
settings for this profile might give you some idea of what you might
need to do.  Where I say "Normally", that reflects the profile where I
do most of my Web surfing.

Images from all domains (Normally, I block images from "other" domains.)

Cookies from 3rd party domains allowed from which there are already
existing cookies and the file cookies.sqlite is marked "read-write".
(Normally, I allow cookies only from the requested domain; and I mark
cookies.sqlite as "read only".)

Popups enabled (Normally, I disable popups.)

FlashBlock extension and HTML5 Media enabled  (Normally, they are
disabled.)

AdBlock Plus and Secret Agent extensions not installed.  (They are
installed in the profile where I do most of my Web surfing.)

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ed Mullen]

On 9/12/2016 at 12:24 PM, Lemuel Johnson's prodigious digits fired off:

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even
evangelist, I have convinced several friends and family members to use
SM as their browser and email client.  They also have Chase accounts.

The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey
again.

So, there was a report that chase.com was usable with the default
SeaMonkey user agent.  That would be good, but I cannot replicate.  My
question is more along the lines of "Am I doing something wrong that
prevents (default) SeaMonkey from being accepted at chase.com?"


Okay, so exactly what is happening when you try to log in?  What message 
does the site give you?


I just went there and tried to log in with fake info and the site 
dutifully directed me to an error page.



--
Ed Mullen
http://edmullen.net/
Have you ever imagined a world with no hypothetical situations?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/11/2016 8:19 PM, Ed Mullen wrote:

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and
statements."


Change banks.




I appreciate the suggestions.  But as a SeaMonkey proponent, maybe even 
evangelist, I have convinced several friends and family members to use 
SM as their browser and email client.  They also have Chase accounts.


The reality is:
1. They are not changing banks.
2. They have no idea what a User Agent is or any desire to learn.
3. They will not use a different browser just to access chase.com
4. If they move to a different browser they will not be using SeaMonkey 
again.


So, there was a report that chase.com was usable with the default 
SeaMonkey user agent.  That would be good, but I cannot replicate.  My 
question is more along the lines of "Am I doing something wrong that 
prevents (default) SeaMonkey from being accepted at chase.com?"

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[WaltS48]

On 09/11/2016 04:31 PM, Lemuel Johnson wrote:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default 
User

Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
Firefox/43.0

SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and 
statements."



Change browsers. I'll bet Firefox works, and you could use it just for 
Chase.



--
Visit Pittsburgh 
Ubuntu 16.04.1 LTS

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/11/2016 6:19 PM, Ed Mullen wrote:
> 
> Change banks.

That is what I suggested more than two weeks ago.

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Keith Thompson]

On 09/11/16 4:50 PM, Lee wrote:

On 9/11/16, Lemuel Johnson  wrote:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and statements."


The current version of firefox is 48.0.2, so I'd try changing the UA
to FF 48 & dropping SeaMonkey:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0

Regards,
Lee

I used that and it worked just fine.  I did have a higher value for rv: (66 I 
think) and it rejected, so dropped back to the 48 and signed right in.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ed Mullen]

On 9/11/2016 at 4:31 PM, Lemuel Johnson's prodigious digits fired off:

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and statements."


Change banks.


--
Ed Mullen
http://edmullen.net/
If you can read this, I can slam on my brakes and sue you.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lee]

On 9/11/16, Lemuel Johnson  wrote:
> On 9/10/2016 12:28 PM, Ed Mullen wrote:
>> On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:
>>> On 9/2/2016 1:56 PM, Arnie Goetchius wrote:
 snipped<
 As of today, I can now log into the Chase website with the default User
 Agent for Seamonkey. This is what my UA shows:

 Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
 Firefox/43.0 SeaMonkey/2.40

>>>
>>> Chase is still not allowing me access.
>>>
>>> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
>>> SeaMonkey/2.40
>>>
>>> I also tried spoofing "Windows NT 10.0" without success.
>>
>> Try clearing out any Chase cookies and make sure you allow them.
>>
>
> Did that first, also cleared cache.  Still no go:
> "You need to upgrade your browser to access your accounts and statements."

The current version of firefox is 48.0.2, so I'd try changing the UA
to FF 48 & dropping SeaMonkey:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0

Regards,
Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/10/2016 12:28 PM, Ed Mullen wrote:

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.



Did that first, also cleared cache.  Still no go:
"You need to upgrade your browser to access your accounts and statements."
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ed Mullen]

On 9/10/2016 at 12:50 PM, Lemuel Johnson's prodigious digits fired off:

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
SeaMonkey/2.40

I also tried spoofing "Windows NT 10.0" without success.


Try clearing out any Chase cookies and make sure you allow them.

--
Ed Mullen
http://edmullen.net/
You can't trust dogs to watch your food.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Lemuel Johnson]

On 9/2/2016 1:56 PM, Arnie Goetchius wrote:

snipped<
As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40



Chase is still not allowing me access.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 
SeaMonkey/2.40


I also tried spoofing "Windows NT 10.0" without success.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ray_Net]

Ed Mullen wrote on 07/09/2016 16:15:

On 9/7/2016 at 7:31 AM, Daniel's prodigious digits fired off:

On 7/09/2016 5:15 AM, Ray_Net wrote:

David E. Ross wrote on 05/09/2016 22:38:

On 9/5/2016 12:17 PM, Ray_Net wrote:

Jerry wrote on 04/09/2016 15:12:

I've been following this thread with much interest, since I had the
same problem with CHASE. I am happy to report that as of today I can
now log into my Chase account with Seamonkey 2.45 on Linux.

I have the User Agent Switcher addon installed. In that I entered a
new User Agent I named Seamonkey. For the User Agent string I have
"Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0". I removed Seamonkey from the end of the string 
(taking

the clue from David's last post), and now it works!

Oh, I did go in and delete all chase.com cookies before I tried 
to log

in to Chase.

Thanks to all of you for not giving up and sorting this out!





As I said before .. SM must ONLY have Firefox in his User Agent
String ...
... when "Advertise Firefox compatibility" is checked.


No, that would indicate Firefox is the browser.  "Advertise Firefox
compatibility" should indicate both SeaMonkey and Firefox.

Actually, when I use PrefBar's user agent spoofing, my user agent
strings is
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40, NOT Firefox/45.0

If I were to enable "Advertise Firefox compatibility", the string
would be
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Many cases of user agent sniffing merely look for "Firefox" without
considering the rest of the string.  It would be better to look for
"Gecko", in which case all this discussion would be moot. Of course,
that would have to change when Gecko is abandoned in favor of 
Servo; but

that replacement is not yet certain.


I just think that if SM say that It is Firefox ... NO problems when
webmasters does bad sniffing.
It's more sites than "a few" .
Most of WebMasters ignore SeaMonkey ... saying : what's that ?
And don't care about "gecko" which is not a browser ...


And as long as they don't know about SeaMonkey or any of the other
browsers that are based on Gecko, the "WebMasters" will never know about
SeaMonkey or any of the other browsers that are based on Gecko!!

I don't think anyone here is suggesting that *you have to*, but then
don't complain when your SeaMonkey Browser that is advertising itself as
Firefox doesn't work as you would expect it to.



The problem is that Web site designers are doing non-standard things 
and shouldn't be.  If they'd design standards-compliant pages there'd 
be no need for sniffing.





That's correct. And in respond to "don't complain when your SeaMonkey 
Browser that is advertising itself as
Firefox doesn't work as you would expect it to." I say: IF Firefox 
render correctly the website SM will do the same.
In addition, you can speak about SeaMonkey to WebMasters ... they will 
continue to ignore this Browser ... they don't care about the great list 
of other Browsers that exist, they support.only their little list.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ed Mullen]

On 9/7/2016 at 7:31 AM, Daniel's prodigious digits fired off:

On 7/09/2016 5:15 AM, Ray_Net wrote:

David E. Ross wrote on 05/09/2016 22:38:

On 9/5/2016 12:17 PM, Ray_Net wrote:

Jerry wrote on 04/09/2016 15:12:

I've been following this thread with much interest, since I had the
same problem with CHASE. I am happy to report that as of today I can
now log into my Chase account with Seamonkey 2.45 on Linux.

I have the User Agent Switcher addon installed. In that I entered a
new User Agent I named Seamonkey. For the User Agent string I have
"Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0". I removed Seamonkey from the end of the string (taking
the clue from David's last post), and now it works!

Oh, I did go in and delete all chase.com cookies before I tried to log
in to Chase.

Thanks to all of you for not giving up and sorting this out!





As I said before .. SM must ONLY have Firefox in his User Agent
String ...
... when "Advertise Firefox compatibility" is checked.


No, that would indicate Firefox is the browser.  "Advertise Firefox
compatibility" should indicate both SeaMonkey and Firefox.

Actually, when I use PrefBar's user agent spoofing, my user agent
strings is
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40, NOT Firefox/45.0

If I were to enable "Advertise Firefox compatibility", the string
would be
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Many cases of user agent sniffing merely look for "Firefox" without
considering the rest of the string.  It would be better to look for
"Gecko", in which case all this discussion would be moot.  Of course,
that would have to change when Gecko is abandoned in favor of Servo; but
that replacement is not yet certain.


I just think that if SM say that It is Firefox ... NO problems when
webmasters does bad sniffing.
It's more sites than "a few" .
Most of WebMasters ignore SeaMonkey ... saying : what's that ?
And don't care about "gecko" which is not a browser ...


And as long as they don't know about SeaMonkey or any of the other
browsers that are based on Gecko, the "WebMasters" will never know about
SeaMonkey or any of the other browsers that are based on Gecko!!

I don't think anyone here is suggesting that *you have to*, but then
don't complain when your SeaMonkey Browser that is advertising itself as
Firefox doesn't work as you would expect it to.



The problem is that Web site designers are doing non-standard things and 
shouldn't be.  If they'd design standards-compliant pages there'd be no 
need for sniffing.





--
Ed Mullen
http://edmullen.net/
Why are cigarettes sold in gas stations when you can't smoke there?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Daniel]

On 7/09/2016 5:15 AM, Ray_Net wrote:

David E. Ross wrote on 05/09/2016 22:38:

On 9/5/2016 12:17 PM, Ray_Net wrote:

Jerry wrote on 04/09/2016 15:12:

I've been following this thread with much interest, since I had the
same problem with CHASE. I am happy to report that as of today I can
now log into my Chase account with Seamonkey 2.45 on Linux.

I have the User Agent Switcher addon installed. In that I entered a
new User Agent I named Seamonkey. For the User Agent string I have
"Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0". I removed Seamonkey from the end of the string (taking
the clue from David's last post), and now it works!

Oh, I did go in and delete all chase.com cookies before I tried to log
in to Chase.

Thanks to all of you for not giving up and sorting this out!





As I said before .. SM must ONLY have Firefox in his User Agent
String ...
... when "Advertise Firefox compatibility" is checked.


No, that would indicate Firefox is the browser.  "Advertise Firefox
compatibility" should indicate both SeaMonkey and Firefox.

Actually, when I use PrefBar's user agent spoofing, my user agent
strings is
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40, NOT Firefox/45.0

If I were to enable "Advertise Firefox compatibility", the string
would be
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Many cases of user agent sniffing merely look for "Firefox" without
considering the rest of the string.  It would be better to look for
"Gecko", in which case all this discussion would be moot.  Of course,
that would have to change when Gecko is abandoned in favor of Servo; but
that replacement is not yet certain.


I just think that if SM say that It is Firefox ... NO problems when
webmasters does bad sniffing.
It's more sites than "a few" .
Most of WebMasters ignore SeaMonkey ... saying : what's that ?
And don't care about "gecko" which is not a browser ...


And as long as they don't know about SeaMonkey or any of the other 
browsers that are based on Gecko, the "WebMasters" will never know about 
SeaMonkey or any of the other browsers that are based on Gecko!!


I don't think anyone here is suggesting that *you have to*, but then 
don't complain when your SeaMonkey Browser that is advertising itself as 
Firefox doesn't work as you would expect it to.


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ray_Net]

David E. Ross wrote on 05/09/2016 22:38:

On 9/5/2016 12:17 PM, Ray_Net wrote:

Jerry wrote on 04/09/2016 15:12:

I've been following this thread with much interest, since I had the
same problem with CHASE. I am happy to report that as of today I can
now log into my Chase account with Seamonkey 2.45 on Linux.

I have the User Agent Switcher addon installed. In that I entered a
new User Agent I named Seamonkey. For the User Agent string I have
"Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0". I removed Seamonkey from the end of the string (taking
the clue from David's last post), and now it works!

Oh, I did go in and delete all chase.com cookies before I tried to log
in to Chase.

Thanks to all of you for not giving up and sorting this out!





As I said before .. SM must ONLY have Firefox in his User Agent String ...
... when "Advertise Firefox compatibility" is checked.


No, that would indicate Firefox is the browser.  "Advertise Firefox
compatibility" should indicate both SeaMonkey and Firefox.

Actually, when I use PrefBar's user agent spoofing, my user agent strings is
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40, NOT Firefox/45.0

If I were to enable "Advertise Firefox compatibility", the string would be
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Many cases of user agent sniffing merely look for "Firefox" without
considering the rest of the string.  It would be better to look for
"Gecko", in which case all this discussion would be moot.  Of course,
that would have to change when Gecko is abandoned in favor of Servo; but
that replacement is not yet certain.

I just think that if SM say that It is Firefox ... NO problems when 
webmasters does bad sniffing.

It's more sites than "a few" .
Most of WebMasters ignore SeaMonkey ... saying : what's that ?
And don't care about "gecko" which is not a browser ...
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[JAS]

David E. Ross wrote:

On 9/5/2016 12:17 PM, Ray_Net wrote:

Jerry wrote on 04/09/2016 15:12:

I've been following this thread with much interest, since I had the
same problem with CHASE. I am happy to report that as of today I can
now log into my Chase account with Seamonkey 2.45 on Linux.

I have the User Agent Switcher addon installed. In that I entered a
new User Agent I named Seamonkey. For the User Agent string I have
"Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0". I removed Seamonkey from the end of the string (taking
the clue from David's last post), and now it works!

Oh, I did go in and delete all chase.com cookies before I tried to log
in to Chase.

Thanks to all of you for not giving up and sorting this out!





As I said before .. SM must ONLY have Firefox in his User Agent String ...
... when "Advertise Firefox compatibility" is checked.



No, that would indicate Firefox is the browser.  "Advertise Firefox
compatibility" should indicate both SeaMonkey and Firefox.

Actually, when I use PrefBar's user agent spoofing, my user agent strings is
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40, NOT Firefox/45.0

If I were to enable "Advertise Firefox compatibility", the string would be
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Many cases of user agent sniffing merely look for "Firefox" without
considering the rest of the string.  It would be better to look for
"Gecko", in which case all this discussion would be moot.  Of course,
that would have to change when Gecko is abandoned in favor of Servo; but
that replacement is not yet certain.

Does not the general.useragent.overide.chase.com;Mozilla/5.0 (Windows NT 
6.1; rv:43.0) Gecko/20100101 Firefox/43.0 not work anymore? It used to 
work in about:config


--
   You either teach people to treat you with dignity and respect, or 
you don't. This means you are partly responsible for the mistreatment 
that you get at the hands of someone else.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/5/2016 12:17 PM, Ray_Net wrote:
> Jerry wrote on 04/09/2016 15:12:
>> I've been following this thread with much interest, since I had the
>> same problem with CHASE. I am happy to report that as of today I can
>> now log into my Chase account with Seamonkey 2.45 on Linux.
>>
>> I have the User Agent Switcher addon installed. In that I entered a
>> new User Agent I named Seamonkey. For the User Agent string I have
>> "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>> Firefox/43.0". I removed Seamonkey from the end of the string (taking
>> the clue from David's last post), and now it works!
>>
>> Oh, I did go in and delete all chase.com cookies before I tried to log
>> in to Chase.
>>
>> Thanks to all of you for not giving up and sorting this out!
>>
>>
>>
>>
> As I said before .. SM must ONLY have Firefox in his User Agent String ...
> ... when "Advertise Firefox compatibility" is checked.
> 

No, that would indicate Firefox is the browser.  "Advertise Firefox
compatibility" should indicate both SeaMonkey and Firefox.

Actually, when I use PrefBar's user agent spoofing, my user agent strings is
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40, NOT Firefox/45.0

If I were to enable "Advertise Firefox compatibility", the string would be
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Many cases of user agent sniffing merely look for "Firefox" without
considering the rest of the string.  It would be better to look for
"Gecko", in which case all this discussion would be moot.  Of course,
that would have to change when Gecko is abandoned in favor of Servo; but
that replacement is not yet certain.

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ray_Net]

Jerry wrote on 04/09/2016 15:12:

I've been following this thread with much interest, since I had the
same problem with CHASE. I am happy to report that as of today I can
now log into my Chase account with Seamonkey 2.45 on Linux.

I have the User Agent Switcher addon installed. In that I entered a
new User Agent I named Seamonkey. For the User Agent string I have
"Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0". I removed Seamonkey from the end of the string (taking
the clue from David's last post), and now it works!

Oh, I did go in and delete all chase.com cookies before I tried to log
in to Chase.

Thanks to all of you for not giving up and sorting this out!





As I said before .. SM must ONLY have Firefox in his User Agent String ...
... when "Advertise Firefox compatibility" is checked.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Jerry]

I've been following this thread with much interest, since I had the
same problem with CHASE. I am happy to report that as of today I can
now log into my Chase account with Seamonkey 2.45 on Linux.

I have the User Agent Switcher addon installed. In that I entered a
new User Agent I named Seamonkey. For the User Agent string I have
"Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0". I removed Seamonkey from the end of the string (taking
the clue from David's last post), and now it works!

Oh, I did go in and delete all chase.com cookies before I tried to log
in to Chase.

Thanks to all of you for not giving up and sorting this out!



On Sun, Sep 4, 2016 at 4:41 AM, Daniel  wrote:
> On 4/09/2016 12:20 AM, WaltS48 wrote:
>>
>> On 09/03/2016 10:07 AM, Daniel wrote:
>>>
>>> On 3/09/2016 11:16 PM, WaltS48 wrote:

 Daniel wrote:
>
> On 3/09/2016 4:56 AM, Arnie Goetchius wrote:


 

>> As of today, I can now log into the Chase website with the default
>> User
>> Agent for Seamonkey. This is what my UA shows:
>>
>> Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>> Firefox/43.0 SeaMonkey/2.40
>>
> Well that's not the default User Agent string, as the default does not
> mention Firefox! See mine below..


 It isn't?

 With the default Edit > Preferences > Advanced > HTTP Networking >
 Advertise Firefox compatibility checked, mine is Mozilla/5.0 (X11; Linux
 x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.

 With it not checked, Mozilla/5.0 (X11; Linux x86_64; rv:43.0)
 Gecko/20100101 SeaMonkey/2.40, which requires the user changing it
 because it is checked by default.
>>>
>>>
>>> I would expect the setting to carry over from one version to another,
>>> so if you had the HTTP pref set in SM 2.39 (or whatever), then it
>>> would have carried over into 2.40
>>>
>>> But I would expect if you did a brand new install, it would be
>>> de-selected!
>>>
>> This computer never had 2.39 on it, and 2.40 was a fresh install. A test
>> profile has the preference checked by default.
>>
> Hmm! O.K., not what I expected!! When SM 2.45 (or whatever) comes out, I'll
> do a clean full install, rather than a part-Update, and see what happens!!
> (If I remember!!)
>
> --
> Daniel
>
> User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
> SeaMonkey/2.40 Build identifier: 20160120202951
> or
> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101
> SeaMonkey/2.38 Build identifier: 20150903203501
> ___
> support-seamonkey mailing list
> support-seamonkey@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-seamonkey



-- 
God bless,
Jerry
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Daniel]

On 4/09/2016 12:20 AM, WaltS48 wrote:

On 09/03/2016 10:07 AM, Daniel wrote:

On 3/09/2016 11:16 PM, WaltS48 wrote:

Daniel wrote:

On 3/09/2016 4:56 AM, Arnie Goetchius wrote:





As of today, I can now log into the Chase website with the default
User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40


Well that's not the default User Agent string, as the default does not
mention Firefox! See mine below..


It isn't?

With the default Edit > Preferences > Advanced > HTTP Networking >
Advertise Firefox compatibility checked, mine is Mozilla/5.0 (X11; Linux
x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.

With it not checked, Mozilla/5.0 (X11; Linux x86_64; rv:43.0)
Gecko/20100101 SeaMonkey/2.40, which requires the user changing it
because it is checked by default.


I would expect the setting to carry over from one version to another,
so if you had the HTTP pref set in SM 2.39 (or whatever), then it
would have carried over into 2.40

But I would expect if you did a brand new install, it would be
de-selected!


This computer never had 2.39 on it, and 2.40 was a fresh install. A test
profile has the preference checked by default.

Hmm! O.K., not what I expected!! When SM 2.45 (or whatever) comes out, 
I'll do a clean full install, rather than a part-Update, and see what 
happens!! (If I remember!!)


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[David E. Ross]

On 9/3/2016 7:07 AM, Daniel wrote:
> On 3/09/2016 11:16 PM, WaltS48 wrote:
>> Daniel wrote:
>>> On 3/09/2016 4:56 AM, Arnie Goetchius wrote:
>>
>> 
>>
 As of today, I can now log into the Chase website with the default User
 Agent for Seamonkey. This is what my UA shows:

 Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
 Firefox/43.0 SeaMonkey/2.40

>>> Well that's not the default User Agent string, as the default does not
>>> mention Firefox! See mine below..
>>
>> It isn't?
>>
>> With the default Edit > Preferences > Advanced > HTTP Networking >
>> Advertise Firefox compatibility checked, mine is Mozilla/5.0 (X11; Linux
>> x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.
>>
>> With it not checked, Mozilla/5.0 (X11; Linux x86_64; rv:43.0)
>> Gecko/20100101 SeaMonkey/2.40, which requires the user changing it
>> because it is checked by default.
> 
> I would expect the setting to carry over from one version to another, so 
> if you had the HTTP pref set in SM 2.39 (or whatever), then it would 
> have carried over into 2.40
> 
> But I would expect if you did a brand new install, it would be de-selected!
> 

The default is to enable "Advertise Firefox compatibility".  I do not
remember when that capability was added to SeaMonkey, but I do remember
unchecking the checkbox to disable it.

Even with it enabled, there are occasional problems.  Some Web servers
or individual Web pages, sniff the user agent (UA) string and find
SeaMonkey at the end:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40
and fail to acknowledge that the request might have come from Firefox.
For that reason, I depend more on the UA spoofing capability of the
PrefBar extension.  That allows me to spoof Firefox without SeaMonkey
and also Chrome, Opera, Internet Explorer, Edge, and Safari.  However,
it also means that I must occasionally determine updated UA strings for
those browsers and edit PrefBar's spoofing list.

-- 
Donald Trump claims everyone likes him.  Does that
include his ex-wives?  How about the students who
discovered that their education at Trump University
was worthless?  And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[WaltS48]

On 09/03/2016 10:07 AM, Daniel wrote:

On 3/09/2016 11:16 PM, WaltS48 wrote:

Daniel wrote:

On 3/09/2016 4:56 AM, Arnie Goetchius wrote:




As of today, I can now log into the Chase website with the default 
User

Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40


Well that's not the default User Agent string, as the default does not
mention Firefox! See mine below..


It isn't?

With the default Edit > Preferences > Advanced > HTTP Networking >
Advertise Firefox compatibility checked, mine is Mozilla/5.0 (X11; Linux
x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.

With it not checked, Mozilla/5.0 (X11; Linux x86_64; rv:43.0)
Gecko/20100101 SeaMonkey/2.40, which requires the user changing it
because it is checked by default.


I would expect the setting to carry over from one version to another, 
so if you had the HTTP pref set in SM 2.39 (or whatever), then it 
would have carried over into 2.40


But I would expect if you did a brand new install, it would be 
de-selected!


This computer never had 2.39 on it, and 2.40 was a fresh install. A test 
profile has the preference checked by default.



--
Visit Pittsburgh 
Extreme vetting - What Native Americans should have started using in 1492
Ubuntu 16.04LTS

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Daniel]

On 3/09/2016 11:16 PM, WaltS48 wrote:

Daniel wrote:

On 3/09/2016 4:56 AM, Arnie Goetchius wrote:





As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40


Well that's not the default User Agent string, as the default does not
mention Firefox! See mine below..


It isn't?

With the default Edit > Preferences > Advanced > HTTP Networking >
Advertise Firefox compatibility checked, mine is Mozilla/5.0 (X11; Linux
x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.

With it not checked, Mozilla/5.0 (X11; Linux x86_64; rv:43.0)
Gecko/20100101 SeaMonkey/2.40, which requires the user changing it
because it is checked by default.


I would expect the setting to carry over from one version to another, so 
if you had the HTTP pref set in SM 2.39 (or whatever), then it would 
have carried over into 2.40


But I would expect if you did a brand new install, it would be de-selected!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Arnie Goetchius]

Daniel wrote:
> On 3/09/2016 4:56 AM, Arnie Goetchius wrote:
>> David E. Ross wrote:
>>> On 8/30/2016 7:01 AM, Ed Mullen wrote:
 On 8/30/2016 at 9:35 AM, JAS's prodigious digits fired off:
> Ed Mullen wrote:
>> On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:
>>> J. Weaver Jr. wrote:
 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."

 Solved that problem here by adding this preference to
 "about:config":

   general.useragent.override.chase.com

 (type "string") with the following value:

   Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101
 Firefox/43.0

 Yes, it'll have to be updated manually as SM advances, but
 WORKS4ME.
 -JW
>>>
>>> Thanks for that.  It does work, but a PITA to remember every time SM
>>> updates.
>>
>> If you put it in a user.js file it will carry over to an update.
>>
>>
> It does not work for me using Windows XP and Seamonkey 2.40, any
> ideas??
> JAS
>

 The full syntax is:

 user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
 NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");

>>>
>>> NOTE WELL:  The semi-colon (;) at the end is mandatory.  Also, I found
>>> that it helps if entries in user.js are alphabetized by the names of the
>>> preference variables; if this is not a SeaMonkey issue, it is at least a
>>> human issue.
>>>
>> As of today, I can now log into the Chase website with the default User
>> Agent for Seamonkey. This is what my UA shows:
>>
>> Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>> Firefox/43.0 SeaMonkey/2.40
>>
> Well that's not the default User Agent string, as the default does not
> mention Firefox! See mine below..
> 
Thanks for the catch. I had been adjusting user.js and I  guess it
finally took.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Ray_Net]

Daniel wrote on 03/09/2016 12:08:

On 3/09/2016 4:56 AM, Arnie Goetchius wrote:

David E. Ross wrote:

On 8/30/2016 7:01 AM, Ed Mullen wrote:

On 8/30/2016 at 9:35 AM, JAS's prodigious digits fired off:

Ed Mullen wrote:

On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to 
"about:config":


  general.useragent.override.chase.com

(type "string") with the following value:

  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 
Firefox/43.0


Yes, it'll have to be updated manually as SM advances, but 
WORKS4ME.

-JW


Thanks for that.  It does work, but a PITA to remember every 
time SM

updates.


If you put it in a user.js file it will carry over to an update.


It does not work for me using Windows XP and Seamonkey 2.40, any 
ideas??

JAS



The full syntax is:

user_pref("general.useragent.override.chase.com", "Mozilla/5.0 
(Windows

NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");



NOTE WELL:  The semi-colon (;) at the end is mandatory.  Also, I found
that it helps if entries in user.js are alphabetized by the names of 
the
preference variables; if this is not a SeaMonkey issue, it is at 
least a

human issue.


As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Well that's not the default User Agent string, as the default does not 
mention Firefox! See mine below..


Anyway; It's a good news ... Chase accept SeaMonkey with Advertise 
Firefox compatibility checked.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[WaltS48]

Daniel wrote:

On 3/09/2016 4:56 AM, Arnie Goetchius wrote:





As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40


Well that's not the default User Agent string, as the default does not
mention Firefox! See mine below..



It isn't?

With the default Edit > Preferences > Advanced > HTTP Networking > 
Advertise Firefox compatibility checked, mine is Mozilla/5.0 (X11; Linux 
x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.


With it not checked, Mozilla/5.0 (X11; Linux x86_64; rv:43.0) 
Gecko/20100101 SeaMonkey/2.40, which requires the user changing it 
because it is checked by default.


Extensions:

ChatZilla   
DOM Inspector   
Lightning   
PDF Viewer
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Daniel]

On 3/09/2016 4:56 AM, Arnie Goetchius wrote:

David E. Ross wrote:

On 8/30/2016 7:01 AM, Ed Mullen wrote:

On 8/30/2016 at 9:35 AM, JAS's prodigious digits fired off:

Ed Mullen wrote:

On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

  general.useragent.override.chase.com

(type "string") with the following value:

  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME.
-JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


If you put it in a user.js file it will carry over to an update.



It does not work for me using Windows XP and Seamonkey 2.40, any ideas??
JAS



The full syntax is:

user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");



NOTE WELL:  The semi-colon (;) at the end is mandatory.  Also, I found
that it helps if entries in user.js are alphabetized by the names of the
preference variables; if this is not a SeaMonkey issue, it is at least a
human issue.


As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40

Well that's not the default User Agent string, as the default does not 
mention Firefox! See mine below..


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey -- Chase Now Working with SM UA Default

[Arnie Goetchius]

David E. Ross wrote:
> On 8/30/2016 7:01 AM, Ed Mullen wrote:
>> On 8/30/2016 at 9:35 AM, JAS's prodigious digits fired off:
>>> Ed Mullen wrote:
 On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:
> J. Weaver Jr. wrote:
>> 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."
>>
>> Solved that problem here by adding this preference to "about:config":
>>
>>  general.useragent.override.chase.com
>>
>> (type "string") with the following value:
>>
>>  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0
>>
>> Yes, it'll have to be updated manually as SM advances, but WORKS4ME.
>> -JW
>
> Thanks for that.  It does work, but a PITA to remember every time SM
> updates.

 If you put it in a user.js file it will carry over to an update.


>>> It does not work for me using Windows XP and Seamonkey 2.40, any ideas??
>>> JAS
>>>
>>
>> The full syntax is:
>>
>> user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows 
>> NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");
>>
> 
> NOTE WELL:  The semi-colon (;) at the end is mandatory.  Also, I found
> that it helps if entries in user.js are alphabetized by the names of the
> preference variables; if this is not a SeaMonkey issue, it is at least a
> human issue.
> 
As of today, I can now log into the Chase website with the default User
Agent for Seamonkey. This is what my UA shows:

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
Firefox/43.0 SeaMonkey/2.40
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ed Mullen]

On 8/30/2016 at 10:42 AM, David E. Ross's prodigious digits fired off:

On 8/30/2016 7:01 AM, Ed Mullen wrote:

On 8/30/2016 at 9:35 AM, JAS's prodigious digits fired off:

Ed Mullen wrote:

On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

  general.useragent.override.chase.com

(type "string") with the following value:

  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME.
-JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


If you put it in a user.js file it will carry over to an update.



It does not work for me using Windows XP and Seamonkey 2.40, any ideas??
JAS



The full syntax is:

user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows
NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");



NOTE WELL:  The semi-colon (;) at the end is mandatory.  Also, I found
that it helps if entries in user.js are alphabetized by the names of the
preference variables; if this is not a SeaMonkey issue, it is at least a
human issue.



When SM loads it reads the user.js file and writes the data into the 
prefs.js file and sorts the preferences there.


Also, be aware that deleting the user.js or any entries in it does NOT 
remove them from prefs.js.


Further, alterations to either .js file needs to be done with SM closed.



--
Ed Mullen
http://edmullen.net/
"That's a hell of an ambition, to be mellow. It's like wanting to be 
senile." -  Randy Newman

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Lee]

On 8/30/16, JAS  wrote:
> Ed Mullen wrote:
>> On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:
>>> J. Weaver Jr. wrote:
 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."

 Solved that problem here by adding this preference to "about:config":

  general.useragent.override.chase.com

 (type "string") with the following value:

  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

 Yes, it'll have to be updated manually as SM advances, but WORKS4ME.
 -JW
>>>
>>> Thanks for that.  It does work, but a PITA to remember every time SM
>>> updates.
>>
>> If you put it in a user.js file it will carry over to an update.
>>
>>
> It does not work for me using Windows XP and Seamonkey 2.40, any ideas??
> JAS

Assuming putting it in user.js is what isn't working for you, please
copy the line from your user.js & paste it into your reply.

If you also add
user_pref("00_user.js.loaded", "user.js load failed");
as the first line of user.js and
user_pref("00_user.js.loaded", "yes");
as the last line then you can look at the results of "about:config"
and see if user.js was loaded completely (00_user.js.loaded = yes) or
if there was a problem loading it (in my case it's usually leaving off
the trailing ";" that breaks things)


If you're using firefox - right - it doesn't work. See
  https://bugzilla.mozilla.org/show_bug.cgi?id=896114
for why they disabled that functionality and
  https://bugzilla.mozilla.org/show_bug.cgi?id=933959
  general.useragent.override.[domain] (about:config entry) stopped working
  VERIFIED WONTFIX

Then take a look at
  http://www.netmarketshare.com/browser-market-share.aspx?qprid=1=0
where firefox is now below 10% market share.  Duh.

Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 8/30/2016 7:01 AM, Ed Mullen wrote:
> On 8/30/2016 at 9:35 AM, JAS's prodigious digits fired off:
>> Ed Mullen wrote:
>>> On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:
 J. Weaver Jr. wrote:
> 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."
>
> Solved that problem here by adding this preference to "about:config":
>
>  general.useragent.override.chase.com
>
> (type "string") with the following value:
>
>  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0
>
> Yes, it'll have to be updated manually as SM advances, but WORKS4ME.
> -JW

 Thanks for that.  It does work, but a PITA to remember every time SM
 updates.
>>>
>>> If you put it in a user.js file it will carry over to an update.
>>>
>>>
>> It does not work for me using Windows XP and Seamonkey 2.40, any ideas??
>> JAS
>>
> 
> The full syntax is:
> 
> user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows 
> NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");
> 

NOTE WELL:  The semi-colon (;) at the end is mandatory.  Also, I found
that it helps if entries in user.js are alphabetized by the names of the
preference variables; if this is not a SeaMonkey issue, it is at least a
human issue.

-- 
David E. Ross

Republicans scream that Hillary Clinton was responsible
for the tragedy in Benghazi.  They conveniently forget
that it was the Republican-controlled Congress that
drastically cut the State Department's budget for
embassy and consulate protection.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ed Mullen]

On 8/30/2016 at 9:35 AM, JAS's prodigious digits fired off:

Ed Mullen wrote:

On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

 general.useragent.override.chase.com

(type "string") with the following value:

 Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME.
-JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


If you put it in a user.js file it will carry over to an update.



It does not work for me using Windows XP and Seamonkey 2.40, any ideas??
JAS



The full syntax is:

user_pref("general.useragent.override.chase.com", "Mozilla/5.0 (Windows 
NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0");



--
Ed Mullen
http://edmullen.net/
"That's a hell of an ambition, to be mellow. It's like wanting to be 
senile." -  Randy Newman

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ed Mullen]

On 8/30/2016 at 5:24 AM, Daniel's prodigious digits fired off:

On 30/08/2016 12:03 AM, Ed Mullen wrote:

On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

 general.useragent.override.chase.com

(type "string") with the following value:

 Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME.
-JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


If you put it in a user.js file it will carry over to an update.


You must have been reading my mind, Ed!! ;-P



:-)

Yep, there were others who also suggested it.


--
Ed Mullen
http://edmullen.net/
I heard that in relativity theory, space and time are the same thing. 
Einstein discovered this when he kept showing up three miles late to 
meetings.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[JAS]

Ed Mullen wrote:

On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

 general.useragent.override.chase.com

(type "string") with the following value:

 Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME. -JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


If you put it in a user.js file it will carry over to an update.



It does not work for me using Windows XP and Seamonkey 2.40, any ideas??
JAS

--
   You either teach people to treat you with dignity and respect, or 
you don't. This means you are partly responsible for the mistreatment 
that you get at the hands of someone else.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Daniel]

On 30/08/2016 12:03 AM, Ed Mullen wrote:

On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

 general.useragent.override.chase.com

(type "string") with the following value:

 Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME. -JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


If you put it in a user.js file it will carry over to an update.


You must have been reading my mind, Ed!! ;-P

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 8/29/2016 4:50 AM, Daniel wrote:
> On 30/06/2016 4:13 AM, Mark B wrote:
>> J. Weaver Jr. wrote:
>>> 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."
>>>
>>> Solved that problem here by adding this preference to "about:config":
>>>
>>>  general.useragent.override.chase.com
>>>
>>> (type "string") with the following value:
>>>
>>>  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0
>>>
>>> Yes, it'll have to be updated manually as SM advances, but WORKS4ME. -JW
>>
>> Thanks for that.  It does work, but a PITA to remember every time SM
>> updates.
> 
> Once upon a time, a user could create a plain text file called user.js 
> and stick personalised prefs in it and those personal prefs would get 
> incorporated into prefs.js (i.e. about:config) each time SM was re-started.
> 
> Does this not apply now??
> 

Most definitely, YES, it still works.  I prefer using user.js in place
of changing preferences via about:config becasue I can insert comments
to remind me of why I have set a particular preference variable.

-- 
David E. Ross

Republicans scream that Hillary Clinton was responsible
for the tragedy in Benghazi.  They conveniently forget
that it was the Republican-controlled Congress that
drastically cut the State Department's budget for
embassy and consulate protection.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ed Mullen]

On 6/29/2016 at 2:13 PM, Mark B's prodigious digits fired off:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

 general.useragent.override.chase.com

(type "string") with the following value:

 Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME. -JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


If you put it in a user.js file it will carry over to an update.


--
Ed Mullen
http://edmullen.net/
"If I only had a little humility, I'd be perfect." - Ted Turner
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Daniel]

On 30/06/2016 4:13 AM, Mark B wrote:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

 general.useragent.override.chase.com

(type "string") with the following value:

 Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME. -JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


Once upon a time, a user could create a plain text file called user.js 
and stick personalised prefs in it and those personal prefs would get 
incorporated into prefs.js (i.e. about:config) each time SM was re-started.


Does this not apply now??

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Philip Chee]

On 30/06/2016 02:13, Mark B wrote:
> J. Weaver Jr. wrote:
>> Mark B wrote:

>> Solved that problem here by adding this preference to "about:config":
>>
>>  general.useragent.override.chase.com
>>
>> (type "string") with the following value:
>>
>>  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

>> Yes, it'll have to be updated manually as SM advances, but WORKS4ME. -JW
> 
> Thanks for that.  It does work, but a PITA to remember every time SM 
> updates.

As well as a normal string I think you can use a REGEXP (regular
expression) to remove the SeaMonkey part of the string e.g. something
like s/SeaMonkey\/d+\ but I don't know if it accepts all regexp or only
a simplified version.

Regular Expressions:
>
https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/RegExp

One of these bugs may tell you what the substitution code actually does:

>
https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced_id=13189419_desc=user%20agent%20override_desc_type=allwordssubstr

Phil


-- 
Philip Chee , 
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Daniel]

On 18/07/2016 6:06 AM, Rick Merrill wrote:

On 7/17/2016 7:58 AM, Daniel wrote:

I just logged into Chase this morning at this URL:

https://chaseonline.chase.com/Logon.aspx?fromLoc=ALL=COLLogon


Did it give you a survey about the web site?


Rick, you may think, from the attributes quoted above, suggest that I 
logged into Chase.


I have no Chase account, so have never logged onto Chase, so the 
attributes, above, have been stuffed up!!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Rick Merrill]

On 7/17/2016 7:58 AM, Daniel wrote:

I just logged into Chase this morning at this URL:

https://chaseonline.chase.com/Logon.aspx?fromLoc=ALL=COLLogon


Did it give you a survey about the web site?


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Daniel]

On 15/07/2016 11:36 PM, David H. Durgee wrote:

Marisa Ciceran wrote:

I have Seamonkey 2.40 installed and am a Chase Bank customer having
experienced the same problems with login as others who have described it
in detail.

As of today (?), Chase Bank no longer gives a warning. Instead, it
refuses to permit any Seamonkey login, including at
https://chaseonline.chase.com/Logon.aspx which was previously
recommended as the workaround.

Any new suggestions?

Thanks,

Marisa


I just logged into Chase this morning at this URL:

https://chaseonline.chase.com/Logon.aspx?fromLoc=ALL=COLLogon

I am using PrefBar to spoof myself as FireFox 43, specifically:

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101
Firefox/43.0

Perhaps adding the extra data to the URL makes the difference?

Dave


Or was it that you don't mention SM at all that makes things work??

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[chokito]

Test with User Agent from Microsoft Internet Explorer 11:

general.useragent.override.chase.com;Mozilla/5.0 (Windows NT 6.1; Trident/7.0; 
rv:11.0) like Gecko

general.useragent.site_specific_overrides;true
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David H. Durgee]

Marisa Ciceran wrote:

I have Seamonkey 2.40 installed and am a Chase Bank customer having
experienced the same problems with login as others who have described it
in detail.

As of today (?), Chase Bank no longer gives a warning. Instead, it
refuses to permit any Seamonkey login, including at
https://chaseonline.chase.com/Logon.aspx which was previously
recommended as the workaround.

Any new suggestions?

Thanks,

Marisa


I just logged into Chase this morning at this URL:

https://chaseonline.chase.com/Logon.aspx?fromLoc=ALL=COLLogon

I am using PrefBar to spoof myself as FireFox 43, specifically:

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0

Perhaps adding the extra data to the URL makes the difference?

Dave
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Desiree]

On 7/14/2016 9:44 PM, Marisa Ciceran wrote:

I have Seamonkey 2.40 installed and am a Chase Bank customer having
experienced the same problems with login as others who have described it
in detail.

As of today (?), Chase Bank no longer gives a warning. Instead, it
refuses to permit any Seamonkey login, including at
https://chaseonline.chase.com/Logon.aspx which was previously
recommended as the workaround.

Any new suggestions?

Thanks,

Marisa


I had a failed hard drive (was replaced 11 months ago and the 
replacement failed without warning last week) so I didn't have access 
until yesterday and I just now tried SeaMonkey 2.40 again with 
ChaseOnline after reading your message.  You are right.


I thought it a bit odd that Chase said I had to go through their 
rigamorole they have if they don't recognize your computer as they 
recognized it a week ago before my D drive died (using SeaMonkey).  I 
was able to login with no warnings about the browser.  Once logged in 
though, I was rudely told that I had to download IE, Fx, Chrome.   I 
have Fx 45.2 ESR that would probably satisfy them but my default browser 
is Pale Moon which will probably get the same treatment as SeaMonkey.  I 
have a number for Chase tech support but it is old so I don't know if it 
still works.  I think they may have just opened  (according to the hours 
I have listed in my old notes).

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Marisa Ciceran]

I have Seamonkey 2.40 installed and am a Chase Bank customer having 
experienced the same problems with login as others who have described it 
in detail.


As of today (?), Chase Bank no longer gives a warning. Instead, it 
refuses to permit any Seamonkey login, including at 
https://chaseonline.chase.com/Logon.aspx which was previously 
recommended as the workaround.


Any new suggestions?

Thanks,

Marisa


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[humptydumpty]

Rick Merrill wrote:

On 6/30/2016 6:46 AM, Desiree wrote:

On 6/28/2016 9:07 PM, 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 Berger



I don't have problems using SeaMonkey 2.40 (with Fx compatibility
checked) at ChaseOnline.  If you are trying to login at Chase main
website do NOT do that! Login there is insecure and has been for many
years.  Always use https://chaseonline.chase.com/Logon.aspx.

I also have NO problems using Pale Moon and logging into
chaseonline.com.  I've been logging into Chase since they first started
online banking and they were the last major bank in the USA to do it.
The only main gripe I have had all these years is that once they
modernized their online banking (it was AWFUL at first compared to other
banks) and offered ChaseOnline is that once, several years ago, they HID
ChaseOnline and were trying to make everyone login INSECURELY on Chase's
main webpage.  That incensed me so I combed their website for one-half
hour searching for chaseonline.  I finally found it buried in an obscure
section of their site.  I was able to login securely and pay my credit
card bill.  I then called Chase's web support team to complain and the
tech's first words were "OMG you found the link to chaseonline?  Really?
  We've been looking all day since it disappeared".  I was told Chase
had decided to hide chaseonline login page because they wanted everyone
to see the ads on the main webpage.  It didn't stay hidden for long and
I was thanked profusely for finding it!


Most of the phishing email I get pretend to be from Chase!  I wouldn't
do business with them if they paid me.



For this link to Chase, the browser nag message now appears after the login.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 7/7/2016 5:31 PM, Lemuel Johnson wrote:
> On 7/6/2016 9:41 AM, WaltS48 wrote:
>> On 06/29/2016 03: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 Berger
>>
>> Send them this link.
>>
>> 
>>
>>
> 
> And mention that of the 10 largest banks in the United States, 8 have 
> websites that are perfectly happy with SeaMonkey. Bank of America gives 
> a warning: "Our site may not work properly..." but doesn't obstruct 
> access.  Only Chase wields the Wand of Doom.
> 
> lj
> 

Also the Vanguard Group (possibly the largest mutual fund group in the
world), Premier America Credit Union, and Unify Financial Credit Union
(two the largest credit unions in the U.S.) have no problem with any use
of Firefox to view accounts and perform transactions.  However, Vanguard
uses an outside service to stream its Webinars (Web-based seminars);
that service has not problem with Firefox but cannot handle SeaMonkey.

-- 
David E. Ross
.

Is it true that Donald Trump refuses to reveal his
income tax returns because he uses so many questionable
loopholes that he pays no taxes?  See
.
 Even if those
loopholes are legal, Trump might be too embarrassed to
admit he pays no taxes.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Lemuel Johnson]

On 7/6/2016 9:41 AM, WaltS48 wrote:

On 06/29/2016 03: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 Berger


Send them this link.






And mention that of the 10 largest banks in the United States, 8 have 
websites that are perfectly happy with SeaMonkey. Bank of America gives 
a warning: "Our site may not work properly..." but doesn't obstruct 
access.  Only Chase wields the Wand of Doom.


lj
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Rick Merrill]

On 6/30/2016 6:46 AM, Desiree wrote:

On 6/28/2016 9:07 PM, 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 Berger



I don't have problems using SeaMonkey 2.40 (with Fx compatibility
checked) at ChaseOnline.  If you are trying to login at Chase main
website do NOT do that! Login there is insecure and has been for many
years.  Always use https://chaseonline.chase.com/Logon.aspx.

I also have NO problems using Pale Moon and logging into
chaseonline.com.  I've been logging into Chase since they first started
online banking and they were the last major bank in the USA to do it.
The only main gripe I have had all these years is that once they
modernized their online banking (it was AWFUL at first compared to other
banks) and offered ChaseOnline is that once, several years ago, they HID
ChaseOnline and were trying to make everyone login INSECURELY on Chase's
main webpage.  That incensed me so I combed their website for one-half
hour searching for chaseonline.  I finally found it buried in an obscure
section of their site.  I was able to login securely and pay my credit
card bill.  I then called Chase's web support team to complain and the
tech's first words were "OMG you found the link to chaseonline?  Really?
  We've been looking all day since it disappeared".  I was told Chase
had decided to hide chaseonline login page because they wanted everyone
to see the ads on the main webpage.  It didn't stay hidden for long and
I was thanked profusely for finding it!


Most of the phishing email I get pretend to be from Chase!  I wouldn't 
do business with them if they paid me.



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[WaltS48]

On 06/29/2016 03: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 Berger


Send them this link.




--
Visit Pittsburgh 
Pittsburgh Bicentennial 

SouthSide Works Exposed 
Deutschtown Music Festival 
Pittsburgh Vintage Grand Prix 

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ant]

On 7/1/2016 7:25 AM, Ed Mullen wrote:

On 7/1/2016 at 9:11 AM, J. Weaver Jr.'s prodigious digits fired off:

Ed Mullen wrote:


No, the best solution is to walk into your local branch of Chase and
tell them that you are moving all of your accounts to Bank Of America
because their Web site is broken.  THAT is what will get their
attention.  Money talks, especially when it walks.


Assuming the local branch's teller cared, or the assistant manager you'd
probably be referred to to close your accounts cared, they have
_nothing_ to do with the design or implementation of the corporate
website.  -JW


Local branches have an incentive to keep customers; and not lose them.
Account closures /are/ noticed at HQ. Managers would react by telling
HQ: They don't need to have anything to do with design of the Web site
to affect its design.


Even if it is just a single customer?
--
"I look at an ant and I see myself: a native South African, endowed by 
nature with a strength much greater than my size so I might cope with 
the weight of a racism that crushes my spirit." --Miriam Makeba
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( )  Chop ANT from its address if e-mailing privately.
Ant is currently not listening to any songs on this computer.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[David E. Ross]

On 7/1/2016 7:48 AM, Felix Miata wrote:
> Ray_Net composed on 2016-07-01 16:23 (UTC+0200):
> 
 1. They don't care ... about one leave.
 2. It's a fact that SEAMONKEY is 99% of the time NOT detected and
 recognized by webmasters ...Do not put your head in the sand like
 ostriches are.
> 
>>> "Do not put your head in the sand"  They will never know about
>>> SeaMonkey (and other compliant Browsers) unless *WE* make them aware
>>> of it!!
> 
>> Yes, but they do not want to increase the list of browsers they support
> 
> Supporting "browsers" is inept design. They need only support functionality. 
> Functionality is more directly tied to browser engines than browser names, 
> but sniffing even engines is inept design.
> 

The problem (as I noted elsewhere in this thread) is with the outside
auditors and with the government regulators.  They want the financial
institutions to certify that they have tested their Web sites for
security and functionality and which browsers were used in those tests.
To avoid negative audit reviews and avoid regulatory discipline, the
financial institutions try to limit access to only those browsers used
in those tests.

I happen to deal with two very large credit unions, a small regional
bank, and a very large mutual fund group.  After much letter-writing
(something else I cited elsewhere in this thread), I got them to
understand that Gecko is Gecko.  I can do transactions through all of
their Web sites with the UA string
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40
and with "Advertise Firefox compatibility" disabled.

Nevertheless, I do have one problem.  The mutual fund group has
Webinars, some of which I want to view.  The Webinars are streamed over
the Internet by a third-party service that requires me to enable
"Advertise Firefox compatibility".  That is easy and quick to handle via
a PrefBar checkbox.

-- 
David E. Ross
.

Is it true that Donald Trump refuses to reveal his
income tax returns because he uses so many questionable
loopholes that he pays no taxes?  See
.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Paul B. Gallagher]

Ray_Net wrote:


Daniel wrote on 01/07/2016 11:42:


"Do not put your head in the sand"  They will never know about
SeaMonkey (and other compliant Browsers) unless *WE* make them aware
of it!!


Yes, but they do not want to increase the list of browsers they support


In that case, they should write W3C-compliant code -- do it once and 
forget about all the sniffing nonsense. That is SO 20th century...


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Felix Miata]

Ray_Net composed on 2016-07-01 16:23 (UTC+0200):


1. They don't care ... about one leave.
2. It's a fact that SEAMONKEY is 99% of the time NOT detected and
recognized by webmasters ...Do not put your head in the sand like
ostriches are.



"Do not put your head in the sand"  They will never know about
SeaMonkey (and other compliant Browsers) unless *WE* make them aware
of it!!



Yes, but they do not want to increase the list of browsers they support


Supporting "browsers" is inept design. They need only support functionality. 
Functionality is more directly tied to browser engines than browser names, 
but sniffing even engines is inept design.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ray_Net]

J. Weaver Jr. wrote on 01/07/2016 15:11:

Ed Mullen wrote:


No, the best solution is to walk into your local branch of Chase and
tell them that you are moving all of your accounts to Bank Of America
because their Web site is broken.  THAT is what will get their
attention.  Money talks, especially when it walks.


Assuming the local branch's teller cared, or the assistant manager 
you'd probably be referred to to close your accounts cared, they have 
_nothing_ to do with the design or implementation of the corporate 
website.  -JW
Exactly, and perhaps their website is created and maintained by another 
company :-)

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ed Mullen]

On 7/1/2016 at 9:11 AM, J. Weaver Jr.'s prodigious digits fired off:

Ed Mullen wrote:


No, the best solution is to walk into your local branch of Chase and
tell them that you are moving all of your accounts to Bank Of America
because their Web site is broken.  THAT is what will get their
attention.  Money talks, especially when it walks.


Assuming the local branch's teller cared, or the assistant manager you'd
probably be referred to to close your accounts cared, they have
_nothing_ to do with the design or implementation of the corporate
website.  -JW


Local branches have an incentive to keep customers; and not lose them. 
Account closures /are/ noticed at HQ. Managers would react by telling 
HQ: They don't need to have anything to do with design of the Web site 
to affect its design.


--
Ed Mullen
http://edmullen.net/
Hospitality:  Making your guests feel like they're at home,  even if you 
wish they were.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ray_Net]

Daniel wrote on 01/07/2016 11:42:

On 1/07/2016 3:35 PM, Ray_Net wrote:

Ed Mullen wrote on 01/07/2016 05:39:

On 6/30/2016 at 3:20 PM, Ray_Net's prodigious digits fired off:

Daniel wrote on 30/06/2016 14:04:

On 30/06/2016 5:09 PM, Ray_Net wrote:

Daniel wrote on 29/06/2016 11:34:

On 29/06/2016 5:07 PM, 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 Berger


Mark, the next time you, or anybody else, gets to talk to the Chase
Bank higher level Tech Support, tell them not to sniff for the word
Firefox but, instead, sniff for the word Gecko.


The webmasters did not know about a browser with the name "Gecko"
... In
fact they don't care about other browsers outside of their list.


And you and I also know that there is no Browser called Gecko, but
(maybe one of the devs will pipe in) is it the programming 
language or

whatever that is called Gecko, so that Chase Bank's Level 2 or higher
will know what is going on??

In the long run, it would provide a better experience for more of
Chase's customers, so they (Chase) should be interested.

So the best solution is that we instead of showing:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101
Firefox/41.0 SeaMonkey/2.38
we show:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101
Firefox/82.38
(just remove 80 from the Firefox version to retrieve the SM version.)
So chase will not tell us to upgrade...



No, the best solution is to walk into your local branch of Chase and
tell them that you are moving all of your accounts to Bank Of America
because their Web site is broken.  THAT is what will get their
attention.  Money talks, especially when it walks.


1. They don't care ... about one leave.
2. It's a fact that SEAMONKEY is 99% of the time NOT detected and
recognized by webmasters ...Do not put your head in the sand like
ostriches are.


"Do not put your head in the sand"  They will never know about 
SeaMonkey (and other compliant Browsers) unless *WE* make them aware 
of it!!



Yes, but they do not want to increase the list of browsers they support
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[J. Weaver Jr.]

Ed Mullen wrote:


No, the best solution is to walk into your local branch of Chase and
tell them that you are moving all of your accounts to Bank Of America
because their Web site is broken.  THAT is what will get their
attention.  Money talks, especially when it walks.


Assuming the local branch's teller cared, or the assistant manager you'd 
probably be referred to to close your accounts cared, they have 
_nothing_ to do with the design or implementation of the corporate 
website.  -JW

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Daniel]

On 1/07/2016 3:35 PM, Ray_Net wrote:

Ed Mullen wrote on 01/07/2016 05:39:

On 6/30/2016 at 3:20 PM, Ray_Net's prodigious digits fired off:

Daniel wrote on 30/06/2016 14:04:

On 30/06/2016 5:09 PM, Ray_Net wrote:

Daniel wrote on 29/06/2016 11:34:

On 29/06/2016 5:07 PM, 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 Berger


Mark, the next time you, or anybody else, gets to talk to the Chase
Bank higher level Tech Support, tell them not to sniff for the word
Firefox but, instead, sniff for the word Gecko.


The webmasters did not know about a browser with the name "Gecko"
... In
fact they don't care about other browsers outside of their list.


And you and I also know that there is no Browser called Gecko, but
(maybe one of the devs will pipe in) is it the programming language or
whatever that is called Gecko, so that Chase Bank's Level 2 or higher
will know what is going on??

In the long run, it would provide a better experience for more of
Chase's customers, so they (Chase) should be interested.

So the best solution is that we instead of showing:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101
Firefox/41.0 SeaMonkey/2.38
we show:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101
Firefox/82.38
(just remove 80 from the Firefox version to retrieve the SM version.)
So chase will not tell us to upgrade...



No, the best solution is to walk into your local branch of Chase and
tell them that you are moving all of your accounts to Bank Of America
because their Web site is broken.  THAT is what will get their
attention.  Money talks, especially when it walks.


1. They don't care ... about one leave.
2. It's a fact that SEAMONKEY is 99% of the time NOT detected and
recognized by webmasters ...Do not put your head in the sand like
ostriches are.


"Do not put your head in the sand"  They will never know about 
SeaMonkey (and other compliant Browsers) unless *WE* make them aware of it!!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ray_Net]

Ed Mullen wrote on 01/07/2016 05:39:

On 6/30/2016 at 3:20 PM, Ray_Net's prodigious digits fired off:

Daniel wrote on 30/06/2016 14:04:

On 30/06/2016 5:09 PM, Ray_Net wrote:

Daniel wrote on 29/06/2016 11:34:

On 29/06/2016 5:07 PM, 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 Berger


Mark, the next time you, or anybody else, gets to talk to the Chase
Bank higher level Tech Support, tell them not to sniff for the word
Firefox but, instead, sniff for the word Gecko.

The webmasters did not know about a browser with the name "Gecko" 
... In

fact they don't care about other browsers outside of their list.


And you and I also know that there is no Browser called Gecko, but
(maybe one of the devs will pipe in) is it the programming language or
whatever that is called Gecko, so that Chase Bank's Level 2 or higher
will know what is going on??

In the long run, it would provide a better experience for more of
Chase's customers, so they (Chase) should be interested.

So the best solution is that we instead of showing:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101
Firefox/41.0 SeaMonkey/2.38
we show:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101
Firefox/82.38
(just remove 80 from the Firefox version to retrieve the SM version.)
So chase will not tell us to upgrade...



No, the best solution is to walk into your local branch of Chase and 
tell them that you are moving all of your accounts to Bank Of America 
because their Web site is broken.  THAT is what will get their 
attention.  Money talks, especially when it walks.



1. They don't care ... about one leave.
2. It's a fact that SEAMONKEY is 99% of the time NOT detected and 
recognized by webmasters ...Do not put your head in the sand like 
ostriches are.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ed Mullen]

On 6/30/2016 at 3:20 PM, Ray_Net's prodigious digits fired off:

Daniel wrote on 30/06/2016 14:04:

On 30/06/2016 5:09 PM, Ray_Net wrote:

Daniel wrote on 29/06/2016 11:34:

On 29/06/2016 5:07 PM, 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 Berger


Mark, the next time you, or anybody else, gets to talk to the Chase
Bank higher level Tech Support, tell them not to sniff for the word
Firefox but, instead, sniff for the word Gecko.


The webmasters did not know about a browser with the name "Gecko" ... In
fact they don't care about other browsers outside of their list.


And you and I also know that there is no Browser called Gecko, but
(maybe one of the devs will pipe in) is it the programming language or
whatever that is called Gecko, so that Chase Bank's Level 2 or higher
will know what is going on??

In the long run, it would provide a better experience for more of
Chase's customers, so they (Chase) should be interested.

So the best solution is that we instead of showing:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101
Firefox/41.0 SeaMonkey/2.38
we show:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101
Firefox/82.38
(just remove 80 from the Firefox version to retrieve the SM version.)
So chase will not tell us to upgrade...



No, the best solution is to walk into your local branch of Chase and 
tell them that you are moving all of your accounts to Bank Of America 
because their Web site is broken.  THAT is what will get their 
attention.  Money talks, especially when it walks.


--
Ed Mullen
http://edmullen.net/
I don't get even, I get odder.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ray_Net]

Daniel wrote on 30/06/2016 14:04:

On 30/06/2016 5:09 PM, Ray_Net wrote:

Daniel wrote on 29/06/2016 11:34:

On 29/06/2016 5:07 PM, 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 Berger


Mark, the next time you, or anybody else, gets to talk to the Chase
Bank higher level Tech Support, tell them not to sniff for the word
Firefox but, instead, sniff for the word Gecko.


The webmasters did not know about a browser with the name "Gecko" ... In
fact they don't care about other browsers outside of their list.


And you and I also know that there is no Browser called Gecko, but 
(maybe one of the devs will pipe in) is it the programming language or 
whatever that is called Gecko, so that Chase Bank's Level 2 or higher 
will know what is going on??


In the long run, it would provide a better experience for more of 
Chase's customers, so they (Chase) should be interested.

So the best solution is that we instead of showing:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101 
Firefox/41.0 SeaMonkey/2.38

we show:
User agent: Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101 
Firefox/82.38

(just remove 80 from the Firefox version to retrieve the SM version.)
So chase will not tell us to upgrade...

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Ed Mullen]

On 6/30/2016 at 9:37 AM, WaltS48's prodigious digits fired off:

On 06/30/2016 08:59 AM, J. Weaver Jr. wrote:

Mason83 wrote:



Why do you have to remember every time SM updates?

Just set Firefox/66.6 and be done with it? :-)


There was some _other_ site (CRS, at the moment) that was actually
doing range checking to block that kind of workaround.  -JW


I use Firefox Beta currently 48.0, and occasionally Firefox Nightly
50.0. Bank of America just started showing this notification:


Our site may not work properly for the browser you're using.See
recommended browsers



Then recommends Firefox 44 or higher. Windows 7 or higher and Mac OS
10.9 or higher.I use a Linux OS.


Not here using FF 48.0b4.

--
Ed Mullen
http://edmullen.net/
Don't be accommodating, be honest.  I honestly don't have much more time 
for anything else.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[WaltS48]

On 06/30/2016 08:59 AM, J. Weaver Jr. wrote:

Mason83 wrote:



Why do you have to remember every time SM updates?

Just set Firefox/66.6 and be done with it? :-)


There was some _other_ site (CRS, at the moment) that was actually 
doing range checking to block that kind of workaround.  -JW


I use Firefox Beta currently 48.0, and occasionally Firefox Nightly 
50.0. Bank of America just started showing this notification:


Our site may not work properly for the browser you're using.See 
recommended browsers 



Then recommends Firefox 44 or higher. Windows 7 or higher and Mac OS 
10.9 or higher.I use a Linux OS.


--
Ban sidewalk patios
Sidewalks are for people to walk down
Restaraunts are for people to eat in
Thank you for your condideration

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[J. Weaver Jr.]

Mason83 wrote:

On 29/06/2016 20:13, Mark B wrote:

J. Weaver Jr. wrote:

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."


Solved that problem here by adding this preference to "about:config":

  general.useragent.override.chase.com

(type "string") with the following value:

  Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0

Yes, it'll have to be updated manually as SM advances, but WORKS4ME. -JW


Thanks for that.  It does work, but a PITA to remember every time SM
updates.


Why do you have to remember every time SM updates?

Just set Firefox/66.6 and be done with it? :-)


There was some _other_ site (CRS, at the moment) that was actually doing 
range checking to block that kind of workaround.  -JW

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase Bank doesn't like SeaMonkey

[Daniel]

On 30/06/2016 5:09 PM, Ray_Net wrote:

Daniel wrote on 29/06/2016 11:34:

On 29/06/2016 5:07 PM, 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 Berger


Mark, the next time you, or anybody else, gets to talk to the Chase
Bank higher level Tech Support, tell them not to sniff for the word
Firefox but, instead, sniff for the word Gecko.


The webmasters did not know about a browser with the name "Gecko" ... In
fact they don't care about other browsers outside of their list.


And you and I also know that there is no Browser called Gecko, but 
(maybe one of the devs will pipe in) is it the programming language or 
whatever that is called Gecko, so that Chase Bank's Level 2 or higher 
will know what is going on??


In the long run, it would provide a better experience for more of 
Chase's customers, so they (Chase) should be interested.


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey