Closed
Bug 52643
Opened 26 years ago
Closed 25 years ago
Wells Fargo doesn't permit latest Mozilla/Netscape PR2 into site
Categories
(Tech Evangelism Graveyard :: English US, defect, P3)
Tech Evangelism Graveyard
English US
Tracking
(Not tracked)
People
(Reporter: ekrock, Assigned: evangelism)
References
()
Details
[ Forwarding this report I received into Bugzilla. IIRC, Wells Fargo is one of
the sites that only allows user agents with recognized strings into its site.
(By default, you can't get in.) So every time we modify the UA string (e.g. for
a new milestone or beta), they have to add that to their list, and in the
meantime, we're locked out. Could someone contact Wells Fargo and ask them to
add the latest Mozilla/Netscape 6 PR2 UA strings to their list of recognized,
approved clients? While we're at it, we should check E*Trade too--they use the
same approach. Long term, it would be great for us to create a list of such
sites and email contacts for each so that each time Netscape/Mozilla/other
Gecko-based clients create a new release, we can notify them by email.
Basically, I think we've discovered another class of bugs here that are ideal
for distributed evangelism. We could also create an email-messager-creator
template HTML page for this like I've done for LAYER/document.all/UA sniffing
issues.]
We are using mozilla:
build id: 2000073008
Mozilla/5.0 (Windows; U; Win98; en-US; m18) Gecko/20000828
Summary :Can't start a secure session with certain sites.
Step to reproduce:
1. Go to banking.wellsfargo.com
Wells Fargo did not recognize the browser type. Following message from wells
fargo was displayed :
"The Browser you are using DOES NOT meet Wells Fargo' striengent security
standard for online banking."
You will see the same behaviour with Mozilla, Netscape 6 (PR 2) as well.
However this site does support Netscape Browser 4.X.
I think this may be a problem related to User Agent string.
------- Additional Comments From Paul Wyskoczka 2000-09-13 11:51 -------
This a problem where Wells Fargo does not recognized Netscape 6 in their list of
supported browsers. This is not a security problem.
Comment 1•26 years ago
|
||
Wells Fargo has a policy of not permitting secure transactions/logins (required
at banking.wellsfargo.com) from beta browsers. Somewhere on the rejection page
they display, there's an FAQ/link that explains their position/rationale.
Comment 2•26 years ago
|
||
still a problem using Netscape6 candidate bits: 2000.10.30.09/8-n6. see also bug
57537. sheesh.
OS: Windows NT → All
Hardware: PC → All
Comment 3•25 years ago
|
||
-> evangelism@telocity.com for my evangelism bugs.
removing the now-depreciated evangelism-related keywords.
setting platform to All.
Assignee: blakeross → evangelism
Comment 4•25 years ago
|
||
*** This bug has been marked as a duplicate of 57537 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 6•25 years ago
|
||
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
Updated•11 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
•