Re: Chase problems - again

[Desiree]

On 9/16/2017 9:37 AM, Lemuel Johnson wrote:

On 9/14/2017 8:19 PM, Desiree wrote:

On 9/14/2017 4:22 AM, Paul B. Gallagher wrote:

Desiree wrote:


Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I
used User Agent Switcher and faked Fx 47 (Win 10) as the user agent.
That got me further but only to the screen where Chase says it
doesn't recognize the user's computer and you have to request a
temporary ID code. I did that but Chase just flipped me to the main
Chase page asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?
Is there a better user agent than the one I tried?


When a site login says it "doesn't recognize" your computer, that
generally means it's looking for the cookie it left at your last session
and can't find it. I get the same stupid $#!+ from Google because I
clear cookies frequently (and always at the end of a browser session),
so they make me jump through all kinds of hoops to read my damn Gmail.
And the failed login requiring you to start over is a strong clue that
cookies are not being accepted.

So check your cookie handling options (in the browser: Tools | Cookie
Manager...). If it says "Block Cookies from This Website," that's the
problem. If it says "Use Default Cookie Permissions," check what your
defaults are at Edit | Preferences | Privacy & Security | Cookies.


I was using Session cookies only and default for all sites is to block
all cookies but I was getting cookies from Chase Online website because
I had changed the permissions for it to accept Session Cookies.

Chase was flipping me over to Chase.com though instead of logging me in
on Chase Online.  I did have Chase.com set to block cookies because I
never go there as I login directly to the credit card via Chase Online
(unless there is a problem like now).
So, I changed permissions for Chase.com to accept Session cookies and
now I am getting a message from Chase that says the browser is outdated.
 That is the message I get with Pale Moon but I think on Pale Moon it
may be because "general.useragent.override.chase.com" shows the string
as Fx 31!  But on SeaMonkey there is no user agent override for chase in
about:config so I don't know why I am now getting that the browser is
outdated.

I deleted all cookies for Chase, restarted SeaMonkey and tried again
with this string "Mozilla/5.0 (Windows NT 6.0; WOW64; rv:40.0)
Gecko/20100101 Firefox/40.0" using User Agent Switcher.  I got further
into login and got to the screen where one is asked for a user ID code
sent to your email, phone, etc.  So, I got the code, put it in and
instead of getting logged in, I got flipped to Chase main web page with
a login box in the upper right corner.  At least I didn't get the
message that SeaMonkey is an outdated browser since Chase thinks I am
using Fx 40.

I'm sick of it.


I use UA Switcher to set:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:54.0) Gecko/20100101
Firefox/54.0

and Chase works fine for me.

Lem Johnson

That one is not in the latest list which is ver. 2.6.4 so did you get 
that from an older list?  There's Fx 52 and Fx 57 (x64).

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

Re: Chase problems - again

[Lemuel Johnson]

On 9/14/2017 8:19 PM, Desiree wrote:

On 9/14/2017 4:22 AM, Paul B. Gallagher wrote:

Desiree wrote:


Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I
used User Agent Switcher and faked Fx 47 (Win 10) as the user agent.
That got me further but only to the screen where Chase says it
doesn't recognize the user's computer and you have to request a
temporary ID code. I did that but Chase just flipped me to the main
Chase page asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?
Is there a better user agent than the one I tried?


When a site login says it "doesn't recognize" your computer, that
generally means it's looking for the cookie it left at your last session
and can't find it. I get the same stupid $#!+ from Google because I
clear cookies frequently (and always at the end of a browser session),
so they make me jump through all kinds of hoops to read my damn Gmail.
And the failed login requiring you to start over is a strong clue that
cookies are not being accepted.

So check your cookie handling options (in the browser: Tools | Cookie
Manager...). If it says "Block Cookies from This Website," that's the
problem. If it says "Use Default Cookie Permissions," check what your
defaults are at Edit | Preferences | Privacy & Security | Cookies.


I was using Session cookies only and default for all sites is to block
all cookies but I was getting cookies from Chase Online website because
I had changed the permissions for it to accept Session Cookies.

Chase was flipping me over to Chase.com though instead of logging me in
on Chase Online.  I did have Chase.com set to block cookies because I
never go there as I login directly to the credit card via Chase Online
(unless there is a problem like now).
So, I changed permissions for Chase.com to accept Session cookies and
now I am getting a message from Chase that says the browser is outdated.
 That is the message I get with Pale Moon but I think on Pale Moon it
may be because "general.useragent.override.chase.com" shows the string
as Fx 31!  But on SeaMonkey there is no user agent override for chase in
about:config so I don't know why I am now getting that the browser is
outdated.

I deleted all cookies for Chase, restarted SeaMonkey and tried again
with this string "Mozilla/5.0 (Windows NT 6.0; WOW64; rv:40.0)
Gecko/20100101 Firefox/40.0" using User Agent Switcher.  I got further
into login and got to the screen where one is asked for a user ID code
sent to your email, phone, etc.  So, I got the code, put it in and
instead of getting logged in, I got flipped to Chase main web page with
a login box in the upper right corner.  At least I didn't get the
message that SeaMonkey is an outdated browser since Chase thinks I am
using Fx 40.

I'm sick of it.


I use UA Switcher to set:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:54.0) Gecko/20100101 
Firefox/54.0


and Chase works fine for me.

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

Re: Chase problems - again

[Lee]

On 9/14/17, Desiree  wrote:
> On 9/14/2017 4:22 AM, Paul B. Gallagher wrote:
>> Desiree wrote:
>>
>>> Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I
>>> used User Agent Switcher and faked Fx 47 (Win 10) as the user agent.
>>> That got me further but only to the screen where Chase says it
>>> doesn't recognize the user's computer and you have to request a
>>> temporary ID code. I did that but Chase just flipped me to the main
>>> Chase page asking for login again.
>>>
>>> Does anything work currently with Chase Online login and SeaMonkey?
>>> Is there a better user agent than the one I tried?
>>
>> When a site login says it "doesn't recognize" your computer, that
>> generally means it's looking for the cookie it left at your last session
>> and can't find it. I get the same stupid $#!+ from Google because I
>> clear cookies frequently (and always at the end of a browser session),
>> so they make me jump through all kinds of hoops to read my damn Gmail.
>> And the failed login requiring you to start over is a strong clue that
>> cookies are not being accepted.
>>
>> So check your cookie handling options (in the browser: Tools | Cookie
>> Manager...). If it says "Block Cookies from This Website," that's the
>> problem. If it says "Use Default Cookie Permissions," check what your
>> defaults are at Edit | Preferences | Privacy & Security | Cookies.
>>
> I was using Session cookies only and default for all sites is to block
> all cookies but I was getting cookies from Chase Online website because
> I had changed the permissions for it to accept Session Cookies.
>
> Chase was flipping me over to Chase.com though instead of logging me in
> on Chase Online.  I did have Chase.com set to block cookies because I
> never go there as I login directly to the credit card via Chase Online
> (unless there is a problem like now).
> So, I changed permissions for Chase.com to accept Session cookies and
> now I am getting a message from Chase that says the browser is outdated.
>   That is the message I get with Pale Moon but I think on Pale Moon it
> may be because "general.useragent.override.chase.com" shows the string
> as Fx 31!  But on SeaMonkey there is no user agent override for chase in
> about:config so I don't know why I am now getting that the browser is
> outdated.
>
> I deleted all cookies for Chase, restarted SeaMonkey and tried again
> with this string "Mozilla/5.0 (Windows NT 6.0; WOW64; rv:40.0)
> Gecko/20100101 Firefox/40.0" using User Agent Switcher.  I got further
> into login and got to the screen where one is asked for a user ID code
> sent to your email, phone, etc.  So, I got the code, put it in and
> instead of getting logged in, I got flipped to Chase main web page with
> a login box in the upper right corner.  At least I didn't get the
> message that SeaMonkey is an outdated browser since Chase thinks I am
> using Fx 40.
>
> I'm sick of it.

Have you tried creating a new profile, not changing anything & seeing
if that works?
If it doesn't work, try again after adding firefox to the ua string:
  edit /preferences
  advanced / http networking
  put a check next to 'advertise firefox compatibility'
If that doesn't work, use a different browser.  But if it *does* work,
think about exactly what it is you're trying to accomplish with all
your tweaks like blocking 3rd party cookies.  (My attitude is that if
you don't want their cookies, don't visit their site.)

Then take a look at addons like request policy continued + noscript or
umatrix that will allow you to create fine-grained controls regarding
3rd party requests, javascript, etc.
Or stay with the standard seamonkey controls, change only one thing at
a time, login to chase, undo the change if you can't login, etc...

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

Re: Chase problems - again

[Paul B. Gallagher]

Desiree wrote:

On 9/14/2017 4:22 AM, Paul B. Gallagher wrote:

Desiree wrote:


Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So,
I used User Agent Switcher and faked Fx 47 (Win 10) as the user
agent. That got me further but only to the screen where Chase
says it doesn't recognize the user's computer and you have to
request a temporary ID code. I did that but Chase just flipped me
to the main Chase page asking for login again.

Does anything work currently with Chase Online login and
SeaMonkey? Is there a better user agent than the one I tried?


When a site login says it "doesn't recognize" your computer, that
generally means it's looking for the cookie it left at your last
session and can't find it. I get the same stupid $#!+ from Google
because I clear cookies frequently (and always at the end of a
browser session), so they make me jump through all kinds of hoops
to read my damn Gmail. And the failed login requiring you to start
over is a strong clue that cookies are not being accepted.

So check your cookie handling options (in the browser: Tools |
Cookie Manager...). If it says "Block Cookies from This Website,"
that's the problem. If it says "Use Default Cookie Permissions,"
check what your defaults are at Edit | Preferences | Privacy &
Security | Cookies.


I was using Session cookies only and default for all sites is to
block all cookies but I was getting cookies from Chase Online website
because I had changed the permissions for it to accept Session
Cookies.

Chase was flipping me over to Chase.com though instead of logging me
in on Chase Online.  I did have Chase.com set to block cookies
because I never go there as I login directly to the credit card via
Chase Online (unless there is a problem like now). So, I changed
permissions for Chase.com to accept Session cookies and now I am
getting a message from Chase that says the browser is outdated. That
is the message I get with Pale Moon but I think on Pale Moon it may
be because "general.useragent.override.chase.com" shows the string as
Fx 31!  But on SeaMonkey there is no user agent override for chase
in about:config so I don't know why I am now getting that the browser
is outdated.

I deleted all cookies for Chase, restarted SeaMonkey and tried again
with this string "Mozilla/5.0 (Windows NT 6.0; WOW64; rv:40.0)
Gecko/20100101 Firefox/40.0" using User Agent Switcher.  I got
further into login and got to the screen where one is asked for a
user ID code sent to your email, phone, etc.  So, I got the code, put
it in and instead of getting logged in, I got flipped to Chase main
web page with a login box in the upper right corner.  At least I
didn't get the message that SeaMonkey is an outdated browser since
Chase thinks I am using Fx 40.

I'm sick of it.


I don't blame you.

Maybe someone else will have a better answer.

--
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 problems - again

[Desiree]

On 9/14/2017 4:22 AM, Paul B. Gallagher wrote:

Desiree wrote:


Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I
used User Agent Switcher and faked Fx 47 (Win 10) as the user agent.
That got me further but only to the screen where Chase says it
doesn't recognize the user's computer and you have to request a
temporary ID code. I did that but Chase just flipped me to the main
Chase page asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?
Is there a better user agent than the one I tried?


When a site login says it "doesn't recognize" your computer, that
generally means it's looking for the cookie it left at your last session
and can't find it. I get the same stupid $#!+ from Google because I
clear cookies frequently (and always at the end of a browser session),
so they make me jump through all kinds of hoops to read my damn Gmail.
And the failed login requiring you to start over is a strong clue that
cookies are not being accepted.

So check your cookie handling options (in the browser: Tools | Cookie
Manager...). If it says "Block Cookies from This Website," that's the
problem. If it says "Use Default Cookie Permissions," check what your
defaults are at Edit | Preferences | Privacy & Security | Cookies.

I was using Session cookies only and default for all sites is to block 
all cookies but I was getting cookies from Chase Online website because 
I had changed the permissions for it to accept Session Cookies.


Chase was flipping me over to Chase.com though instead of logging me in 
on Chase Online.  I did have Chase.com set to block cookies because I 
never go there as I login directly to the credit card via Chase Online 
(unless there is a problem like now).
So, I changed permissions for Chase.com to accept Session cookies and 
now I am getting a message from Chase that says the browser is outdated. 
 That is the message I get with Pale Moon but I think on Pale Moon it 
may be because "general.useragent.override.chase.com" shows the string 
as Fx 31!  But on SeaMonkey there is no user agent override for chase in 
about:config so I don't know why I am now getting that the browser is 
outdated.


I deleted all cookies for Chase, restarted SeaMonkey and tried again 
with this string "Mozilla/5.0 (Windows NT 6.0; WOW64; rv:40.0) 
Gecko/20100101 Firefox/40.0" using User Agent Switcher.  I got further 
into login and got to the screen where one is asked for a user ID code 
sent to your email, phone, etc.  So, I got the code, put it in and 
instead of getting logged in, I got flipped to Chase main web page with 
a login box in the upper right corner.  At least I didn't get the 
message that SeaMonkey is an outdated browser since Chase thinks I am 
using Fx 40.


I'm sick of it.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase problems - again

[Desiree]

On 9/14/2017 4:10 AM, Paul B. Gallagher wrote:

Desiree wrote:


On 9/14/2017 1:07 AM, Arnie Goetchius wrote: than the one I tried?

I just logged in with no problem. See my UA for what I use


Why did I just get a Message Security from Thunderbird when I clicked
to reply to you?

I don't see your UA.


CTRL-U on his message to see the full headers:

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101
Firefox/51.0 SeaMonkey/2.48

I didn't notice that I needed to scroll down to see all the headers.  I 
see it now.  The UA I am using is exactly the same except not Windows 10 
but Windows NT 6.2.

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

Re: Chase problems - again

[Desiree]

On 9/14/2017 4:50 AM, Mason83 wrote:

On 14/09/2017 15:40, Desiree wrote:

On 9/14/2017 1:03 AM, Mason83 wrote:

On 14/09/2017 12:18, Desiree wrote:

Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used
User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That
got me further but only to the screen where Chase says it doesn't
recognize the user's computer and you have to request a temporary ID
code.  I did that but Chase just flipped me to the main Chase page
asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?  Is
there a better user agent than the one I tried?


Maybe you can try with an actual FF account.
If that works, try spoofing the same UA in SM?


I spent over an hour last night with Chase (three different agents
purported to be from Chase's online support) and they were of no help
with Firefox (I have Fx 45.9 ESR and Chase accepts Fx from ver 37 up)
and no help with Pale Moon or SeaMonkey.


Does the site work or not with FF 45 ESR?
BTW, you should probably try with FF 52 ESR

It worked with Fx 45.9 ESR once I created a brand new profile with NO 
extensions, no modifications of preferences.

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

Re: Chase problems - again

[Mark B]

Ed Mullen wrote:

On 9/14/2017 at 6:18 AM, Desiree created this epitome of digital genius:

Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used
User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That
got me further but only to the screen where Chase says it doesn't
recognize the user's computer and you have to request a temporary ID
code.  I did that but Chase just flipped me to the main Chase page
asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?  Is
there a better user agent than the one I tried?


I have no trouble logging in with SM 2.48 if I set the Firefox user 
agent BEFORE I go to the site.  Using User Agent Switcher.





No problems logging in to chase.com. SM 64 bit 2.51

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) 
Gecko/20100101 SeaMonkey/2.51

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

Re: Chase problems - again

[Ed Mullen]

On 9/14/2017 at 6:18 AM, Desiree created this epitome of digital genius:

Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used
User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That
got me further but only to the screen where Chase says it doesn't
recognize the user's computer and you have to request a temporary ID
code.  I did that but Chase just flipped me to the main Chase page
asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?  Is
there a better user agent than the one I tried?


I have no trouble logging in with SM 2.48 if I set the Firefox user 
agent BEFORE I go to the site.  Using User Agent Switcher.




--
Ed Mullen
http://edmullen.net/
If a pig loses its voice, is it disgruntled?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase problems - again

[Mason83]

On 14/09/2017 15:40, Desiree wrote:
> On 9/14/2017 1:03 AM, Mason83 wrote:
>> On 14/09/2017 12:18, Desiree wrote:
>>> Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used
>>> User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That
>>> got me further but only to the screen where Chase says it doesn't
>>> recognize the user's computer and you have to request a temporary ID
>>> code.  I did that but Chase just flipped me to the main Chase page
>>> asking for login again.
>>>
>>> Does anything work currently with Chase Online login and SeaMonkey?  Is
>>> there a better user agent than the one I tried?
>>
>> Maybe you can try with an actual FF account.
>> If that works, try spoofing the same UA in SM?
>
> I spent over an hour last night with Chase (three different agents 
> purported to be from Chase's online support) and they were of no help 
> with Firefox (I have Fx 45.9 ESR and Chase accepts Fx from ver 37 up) 
> and no help with Pale Moon or SeaMonkey.

Does the site work or not with FF 45 ESR?
BTW, you should probably try with FF 52 ESR
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase problems - again

[Paul B. Gallagher]

Desiree wrote:


Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I
used User Agent Switcher and faked Fx 47 (Win 10) as the user agent.
That got me further but only to the screen where Chase says it
doesn't recognize the user's computer and you have to request a
temporary ID code. I did that but Chase just flipped me to the main
Chase page asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?
Is there a better user agent than the one I tried?


When a site login says it "doesn't recognize" your computer, that 
generally means it's looking for the cookie it left at your last session 
and can't find it. I get the same stupid $#!+ from Google because I 
clear cookies frequently (and always at the end of a browser session), 
so they make me jump through all kinds of hoops to read my damn Gmail. 
And the failed login requiring you to start over is a strong clue that 
cookies are not being accepted.


So check your cookie handling options (in the browser: Tools | Cookie 
Manager...). If it says "Block Cookies from This Website," that's the 
problem. If it says "Use Default Cookie Permissions," check what your 
defaults are at Edit | Preferences | Privacy & Security | Cookies.


--
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 problems - again

[Paul B. Gallagher]

Desiree wrote:


On 9/14/2017 1:07 AM, Arnie Goetchius wrote: than the one I tried?

I just logged in with no problem. See my UA for what I use


Why did I just get a Message Security from Thunderbird when I clicked
to reply to you?

I don't see your UA.


CTRL-U on his message to see the full headers:

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 
Firefox/51.0 SeaMonkey/2.48


--
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 problems - again

[Richard Owlett]

On 09/14/2017 08:52 AM, Desiree wrote:

On 9/14/2017 1:20 AM, Richard Owlett wrote:

On 09/14/2017 05:18 AM, Desiree wrote:

Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used
User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That
got me further but only to the screen where Chase says it doesn't
recognize the user's computer and you have to request a temporary ID
code.  I did that but Chase just flipped me to the main Chase page
asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?  Is
there a better user agent than the one I tried?


I doubt the problem is SeaMonkey.
I have noticed a number of complaints here in the past few months of
people having problems with sites of {for want of a better term - "mass
market sites"}. I'd take my business elsewhere - did that with Chase
decades ago over different problem but with likely similar root causes.



There's a long, long history of problems with Chase and SeaMonkey and
other browsers but especially SeaMonkey.

I've had a Chase credit card since before Chase even had online
presence.  It is my only card with a FIXED APR at a low rate (lowest of
all my cards) and high credit limit.  So, not one I can walk away from.
 I would do so with other cards whose websites gave me problems, but,
ironically, only Chase has a history, from the beginning of their online
presence, of giving many users headaches with various browsers.


It was their credit card incompetency which caused me to go elsewhere in 
the early 80's.



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

Re: Chase problems - again

[Desiree]

On 9/14/2017 1:20 AM, Richard Owlett wrote:

On 09/14/2017 05:18 AM, Desiree wrote:

Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used
User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That
got me further but only to the screen where Chase says it doesn't
recognize the user's computer and you have to request a temporary ID
code.  I did that but Chase just flipped me to the main Chase page
asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?  Is
there a better user agent than the one I tried?


I doubt the problem is SeaMonkey.
I have noticed a number of complaints here in the past few months of
people having problems with sites of {for want of a better term - "mass
market sites"}. I'd take my business elsewhere - did that with Chase
decades ago over different problem but with likely similar root causes.


There's a long, long history of problems with Chase and SeaMonkey and 
other browsers but especially SeaMonkey.


I've had a Chase credit card since before Chase even had online 
presence.  It is my only card with a FIXED APR at a low rate (lowest of 
all my cards) and high credit limit.  So, not one I can walk away from. 
 I would do so with other cards whose websites gave me problems, but, 
ironically, only Chase has a history, from the beginning of their online 
presence, of giving many users headaches with various browsers.

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

Re: Chase problems - again

[Desiree]

On 9/14/2017 1:03 AM, Mason83 wrote:

On 14/09/2017 12:18, Desiree wrote:

Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used
User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That
got me further but only to the screen where Chase says it doesn't
recognize the user's computer and you have to request a temporary ID
code.  I did that but Chase just flipped me to the main Chase page
asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?  Is
there a better user agent than the one I tried?


Maybe you can try with an actual FF account.
If that works, try spoofing the same UA in SM?

Regards

I spent over an hour last night with Chase (three different agents 
purported to be from Chase's online support) and they were of no help 
with Firefox (I have Fx 45.9 ESR and Chase accepts Fx from ver 37 up) 
and no help with Pale Moon or SeaMonkey.

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

Re: Chase problems - again

[Desiree]

On 9/14/2017 1:07 AM, Arnie Goetchius wrote:

Desiree wrote:

Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used User 
Agent Switcher and
faked Fx 47 (Win 10) as the user agent.  That got me further but only to the 
screen where Chase says
it doesn't recognize the user's computer and you have to request a temporary ID 
code.  I did that
but Chase just flipped me to the main Chase page asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?  Is there a 
better user agent
than the one I tried?

I just logged in with no problem. See my UA for what I use



Why did I just get a Message Security from Thunderbird when I clicked to 
reply to you?


I don't see your UA.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase problems - again

[Richard Owlett]

On 09/14/2017 05:18 AM, Desiree wrote:

Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used
User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That
got me further but only to the screen where Chase says it doesn't
recognize the user's computer and you have to request a temporary ID
code.  I did that but Chase just flipped me to the main Chase page
asking for login again.

Does anything work currently with Chase Online login and SeaMonkey?  Is
there a better user agent than the one I tried?


I doubt the problem is SeaMonkey.
I have noticed a number of complaints here in the past few months of 
people having problems with sites of {for want of a better term - "mass 
market sites"}. I'd take my business elsewhere - did that with Chase 
decades ago over different problem but with likely similar root causes.



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

Re: Chase problems - again

[Arnie Goetchius]

Desiree wrote:
> Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used User 
> Agent Switcher and
> faked Fx 47 (Win 10) as the user agent.  That got me further but only to the 
> screen where Chase says
> it doesn't recognize the user's computer and you have to request a temporary 
> ID code.  I did that
> but Chase just flipped me to the main Chase page asking for login again.
> 
> Does anything work currently with Chase Online login and SeaMonkey?  Is there 
> a better user agent
> than the one I tried?
I just logged in with no problem. See my UA for what I use
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Chase problems - again

[Mason83]

On 14/09/2017 12:18, Desiree wrote:
> Sigh.  I can't login to Chase Online using  SeaMonkey 2.48.  So, I used 
> User Agent Switcher and faked Fx 47 (Win 10) as the user agent.  That 
> got me further but only to the screen where Chase says it doesn't 
> recognize the user's computer and you have to request a temporary ID 
> code.  I did that but Chase just flipped me to the main Chase page 
> asking for login again.
> 
> Does anything work currently with Chase Online login and SeaMonkey?  Is 
> there a better user agent than the one I tried?

Maybe you can try with an actual FF account.
If that works, try spoofing the same UA in SM?

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