Closed Bug 858150 Opened 11 years ago Closed 11 years ago

Chase.com shows server error

Categories

(Firefox :: Untriaged, defect)

20 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jlerner10, Unassigned)

Details

Attachments

(1 file)

Attached image FF connection error.jpg
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130326150557

Steps to reproduce:

Trying to access chase.com


Actual results:

I am using Firefox 20.0 and when I go to https://chase.com or https://chaseonline.chase.com/Logon.aspx I am seeing this

Problem loading page

The connection was reset
The connection to the server was reset while the page was loading.

The site could be temporarily unavailable or too busy. Try again in a few
moments.
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

Try Again

I do not get this using FF19 or if I change the rendering to IE.

This problem was also posted at http://forums.mozillazine.org/viewtopic.php?f=38&t=2686595

My final entries are:

I just reinstalled a clean version of FF 20, which included the removal of all entries in the register.
There are no extensions installed and the plugins are the normal ones such as Acrobat, Flash, Shockwave, Silverlight, Windows Activation and Windows Live Photo.

I tried to access the Chase site again and I am getting the same results.
See Console Error.
Not sure if this will help in finding a solution.
http://i886.photobucket.com/albums/ac69 ... ee0697.jpg

Kind of strange since it works in FF 19 and FF 21.

I installed FF 20 on my laptop and it has Windows XP SP3 on it and I am able to get to the Chase site without a problem.

My Windows 7 SP1 is only about 3 weeks old.

See attached for the error screen.



Expected results:

I should have either gotten the chase web site or the log on page.
The problem appears to occur only with version 20 on Windows 7, not OSX, Linux, or Windows XP.  At least three other users report the same problem.  There is more discussion here:  http://forums.mozillazine.org/viewtopic.php?f=38&t=2686595 .  The OP has posted a Console Error screenshot here:  http://postimg.org/image/gawat8o1l/ .
I can confirm the problem on a Win7/x86 rig after updating to Fx 20.0.
There was no problem at the site with 19.0.2.

At least one of my two Win7/x64 rigs works just fine -- https://www.chase.com webpage renders properly and I have no trouble logging in.

Will attempt to post error console screenshot from the affected x86 rig (and confirmation of NO problem on the other x64 rig) ASAP, hopefully later tonight.

Please let me know if I can assist in any way (longtime Fx user, but tender newbie here at bugzilla).
(In reply to RM from comment #2)

> 
> Will attempt to post <snip>
> confirmation of NO problem on the other x64 rig) ASAP, hopefully later
> tonight.
> 

I have now verified that the problem is indeed isolated only to the Win7/x86 platform.
The web page performs normally on both of my Win7/x64 rigs.

Thank you.
I should (forgot) have mentioned that my system is Windows 7 Pro SP1 32 bit.
>which included the removal of all entries in the register.
That is not necessary if you have issues with content (webpages)

What happens with a new profile ?
http://support.mozilla.org/de/kb/Managing%20profiles
Same error with new profile and as I noted in my OP it also happen after a clean install.

You said ">which included the removal of all entries in the register.
That is not necessary if you have issues with content (webpages)"

This was part of my uninstalling process to insure that Firefox was not on my system before I reinstalled FF 20.
X86 or x64 as platform doesn't matter because you are using the same build (32bit).
Do you have some third party firewall or security software installed ?

I can't reproduce this with Firefox20 or Seamonkey trunk on Windows7

Could you try to find the regression range:
http://support.mozilla.org/de/kb/Managing%20profiles
Ir seems that those who are having a problem are using Windows 7 32 bit. Check the form link that I posted in my OP.
Even RM in the above post noted that the problem existed on his/her Win7/x86 system.

I do use Private Firewall and Avast 8 Free. 
Even with both turned off the error is still there.

Your link(s) are going to a German language support site.
@ :Matti:

For me, a new, naked profile makes no difference (nor does manipulating anything in Fx privacy settings, cookies, numerical address, firewall/AV, mozilla safe mode or anything else suggested here: http://forums.mozillazine.org/viewtopic.php?f=38&t=2686595).

I know it should not matter if the OS is x86 or x64, but it does. Both x64 rigs connect just fine. Only the x86 rig does not.  All 3 run the identical security suite.

And, thus far at least, chase.com is the ONLY affected site.

I am just a home user and don't have a "test box" with which to do much high-level experimentation or testing of a regression range.
But I am quite certain that there was no problem with 19.0.2 or prior versions.

Thank you.
Sorry for the german link, the stupid server always sends me to the german version and I didn't noticed it this time.
This is the right one: http://support.mozilla.org/kb/Managing%20profiles

>I know it should not matter if the OS is x86 or x64, but it does
In that case you just discovered that it's not a Firefox bug since Firefox behaves identical on 32 vs 64bit because we don't have a public 64bit version.

To clarify some things: Reporting this bug here is fine but will not change anything if the reason for this can not be found.

>I do use Private Firewall and Avast 8 Free. 
>Even with both turned off the error is still there.

Turning them off doesn't remove the driver that they added in the networking stack of windows. It would be good to know if affected users are also using this products.

Another way to proceed would be to find the first bad and the last good build with this tool:
http://mozilla.github.com/mozregression/
Matthias,

You said you can not reproduce this problem but you did not say what version of Windows you are using.

But if it is the Windows 7 32 bit and not Firefox why would Firefox 19 and 21 work?
(In reply to Matthias Versen [:Matti] from comment #10)
>
> >I know it should not matter if the OS is x86 or x64, but it does
> In that case you just discovered that it's not a Firefox bug since Firefox
> behaves identical on 32 vs 64bit because we don't have a public 64bit
> version.

Indeed.
With my limited knowledge, I would tend to agree.
However, other browsers (IE9 and Safari) load the same page just fine on the Win7/x86 rig.
So, the problem is unique to Fx.

> 
> To clarify some things: Reporting this bug here is fine but will not change
> anything if the reason for this can not be found.

Understood.
FWIW, I & at least 1 other user did contact Chase Internet Support yesterday. They were surprisingly receptive to the report, recorded all relevant info (including links both to this bug report & to the relevant MZ forum thread), & assigned a ticket number. They promised to be back in touch with me after a few days to investigate.



> 
> >I do use Private Firewall and Avast 8 Free. 
> >Even with both turned off the error is still there.
> 
> Turning them off doesn't remove the driver that they added in the networking
> stack of windows. It would be good to know if affected users are also using
> this products.

KIS2013 on all 3 rigs (both the 2 Win7/x64 that work fine, and the Win7/x86 that does not).


> 
> Another way to proceed would be to find the first bad and the last good
> build with this tool:
> http://mozilla.github.com/mozregression/

That looks to be far over my head from a technical standpoint, but I will see if I can use the tool & report back.

Thank you for your ongoing input and advice.
>But if it is the Windows 7 32 bit and not Firefox why would Firefox 19 and 21 work?
Firefox21 is working ?
We can close this report in that case because the next update for Firefox20 should be Firefox21.
Why close the report without finding out why?
If it happens once it could happen again.

Find the problem now and that way if it happens again you will know why and be able to fix it if this problem shows up again.
>Why close the report without finding out why?
Why spend hours on something while the time could be sepnd much better on still existing issues.
There is nothing to do for the developers or bug triagers if this is already fixed in Firefox21.

Only you (and other users who are able to see the issue) can find the source code change that caused it and also what fixed it by finding the regression range. The regression range from nightly builds is in some cases not enough and you have to bisect and build the source code with different changesets.
That work can only be done by you or some other affected user. Finding the regression range with nightly builds is fast (10min) but bisecting will take hours.
Apparently a case of browser sniffing.
https://support.mozilla.org/en-US/questions/955701

Thanks, dickvl, for finding it.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: