Closed
Bug 277960
Opened 20 years ago
Closed 16 years ago
usbank.com - Can not access Bill Pay
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tech Evangelism Graveyard
English US
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jayclark, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 After logging on to US Bank, an attempt to go to Internet Bill Pay results in being returned to the Log In screen. I sincerely apologize for duplicating bug #169008, but it would not let me re-open it or add a comment. The text of my attempted comment is below. I currently experience this exact error in Firefox (all versions) on Linux, Windows 2000, and Windows XP. The rest of the website (as far as I can tell) works. Phone calls w/ US Bank's tech support yielded only a promise to try to mention the problem to the web developers. Reproducible: Always Steps to Reproduce: 1. Access www.usbank.com/internet_banking_logon 2. Enter "Personal ID", "Password", and choose "Bill Pay" as your destination, then click "Login". OR 1. Login as before but leave the destination as "Your Accounts". This time login is successful. 2. Click "Bill Pay" in the left-side navigation column. Actual Results: The browser appears to contact https://www4.usbank.com/internetBanking/RequestRouter then tries connecting to www.thevalidnetwork.com. The status bar shows that it is waiting for a connection to www.thevalidnetwork.com then returns me to the Internet Banking login page. Expected Results: The page should have sent me to the "Bill Pay" portion of the USBank website.
Note: The Bill Pay portion of the usbank.com website is accessible with current Mozilla versions and as far back as version 0.9 I think.
Comment 2•20 years ago
|
||
Thanks Jay! marking fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Reopening the bug. The note was meant to clarify that the website's Bill Pay section is accessible by new and old versions of the Mozilla Browser, but it is still broken for Firefox. I apologize for the ambiguity, I assumed "Mozilla" would be understood as "Mozilla" and not "Mozilla Firefox."
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Comment 4•20 years ago
|
||
doh! sorry! Jay, to isolate if this is pure browser detection and not some Firefox only bug, can you use Mozilla, spoof your user agent to be Firefox 1.0 and see if the problem still occurs? If not, can you try a recent Firefox trunk build and reproduce using that? There is a user agent switcher at mozdev which can do the spoof or you can use the ua sidebar at <http://bclary.com/2004/06/06/sidebars>. After you are finished with the Firefox trunk build, you may want to reinstall Firefox 1.0 since the trunk is "kind of" flakey these days.
Okay, here's what I've done. I used the bclary UA switcher in Mozilla 1.7.3 with the following UAs selected: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041115 Firefox/1.0 Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.7.5) Gecko/20041115 Firefox/1.0 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041115 Firefox/1.0 All of them work properly--I am able to log in to Bill Pay. I noticed that Firefox on my machine had a UA with this "Gecko/20041111" instead of what is listed above. So I also used the "User Agent Switcher" extension by Chris Pederick to see if the change in UA in Firefox would make a difference. It didn't--I am still unable to log in to Bill Pay with an updated UA in Firefox 1.0. I also tried a nightly build from 2005.01.29, which also does not work for logging in to Bill Pay. Let me know if there's any other way I can help.
Not sure how much this new observation will help... I noticed when trying to log in that Firefox's titlebar shows: "U.S. Bank | Web Bill Pay" which is what it should say if I were actually logged in. It seems to me that the Bill Pay page gets partially loaded (at least the <title> tag gets read) and then I get kicked back out to the login screen.
Comment 7•20 years ago
|
||
Jay, let me summarize to see if I have situation: Mozilla 1.7.3/Windows was able to log into Bill Pay successfully regardless of the UA setting, but Mozilla Firefox 1.0/Windows was not able to do so. It may have actually logged in but then ended back up at the login screen. My feeling at this point is this is a browser bug and not an evangelism issue. Jay, can you test with the following builds and let me know which ones succeed or fail in logging in? Mozilla 1.7.5 release build <ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.5/> a recent Mozilla 1.7.6 nightly <ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-1.7/> a recent Mozilla trunk nightly <ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/> a recent Firefox trunk nightly <ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/> I can't seem to find a recent Firefox nightly from the 1.7 branch, but if you can find one and test that it would be great too. Thanks.
Comment 8•20 years ago
|
||
PS. Please check to make sure your Firefox profile allows cookies for usbank.com
I'm sure that my profile allows cookies (Windows and Linux). I have tried logging in to Bill Pay with cookies on and set to "until they expire," and "ask me every time." Both settings have the same effect--unable to login to Bill Pay.
Comment 10•16 years ago
|
||
Jay, is this still a problem three years later? https://www4.usbank.com/internetBanking/en_us/info/BrowserRequirementsOut.jsp seems to indicate they support Firefox, and I can enter a garbage login/password and get a proper error page without running into any "unsupported browser" messages.
Comment 11•16 years ago
|
||
Sounds FIXED absent any comments to the contrary. If someone sees this again, please open a NEW bug on the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 16 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•