142145 - Selecting account history causes server to log off the user

Status: VERIFIED WORKSFORME

(Core :: Networking: HTTP, defect)

Description

[Daniel Nilsson]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020417
BuildID:    2002041711

Using the online banking at citizensonline.com I can login just fine with
mozilla and see the account summary page. When I go to see the account history
however I'm automatically logged off the service with error message #1004 "You
where automatically logged off".

I'm using 1.0rc1 of mozilla on i386 Linux (SuSE 7.3). What's interesting here is
that this used to work just fine with older builds of mozilla. I went back to
0.9.9 and it works (I tried to login several times and select the account
history). Using 0.9.4 I get the same problem as with 1.0rc1. I built the latest
CVS off of the 1_0_branch (help about says 1.0rc2) and that also gives me the
same problem. So the only version that works is 0.9.4...

I did expect this to be reported already, I can't find anything matching
though...  I'm also not sure which component this belongs to or how to help
debug  this problem. 

If you need to debug this on a real account I can provide my login information
to you (no, not really, just kidding...)


Reproducible: Always
Steps to Reproduce:
1. Login to citizensbankonline
2. Select history for one of the accounts
3.

Actual Results:  You get logged off with error message #1004 (error message from
the web server)

Expected Results:  Account history shown

Comment 1

[benc]

-> HTTP, fixed URL

Comment 2

[benc]

*** Bug 142151 has been marked as a duplicate of this bug. ***

Comment 3

[Daniel Nilsson]

I did try a couple of more things here. First I did an optimized debug build of
1.0rc2, this build segfaults when trying to launch mozilla though. I did not
investigate this further.

So then I did an non-optimized debug build of the same source (1.0rc2) and now I
can use the online banking service as expected (ie, it works the same way as
with 0.9.4).

I should mention that the 1.0rc1 build I reported this against I downloaded from
mozilla.org, I didn't build it myself.

Comment 4

[Daniel Nilsson]

This seems to work now, using mozilla 1.0. Don't know if the website was fixed
or is this problem went away using version 1.0 of Mozilla, but this bug can be
closed.

Comment 5

[Tom Everingham]

verified per reporters comments