user will be greeted with: -- your security comes first Unfortunately the browser you are using does not support our high levels of security. Click on one of the links below to download a free copy of either Microsoft Internet Explorer Version 4 or above, or Netscape Communicator Version 4.6 or above. Click here to download Internet Explorer Click here to download Netscape Communicator Please note that Netscape 6.0 is not supported by our site. -- sounds absurd [will work with Konqueror masquerading as N4]
According to their faq http://www.zurichbank.co.uk/homesuite/q_security.html , Netscape 6.x is supported (minus 6.0), thus Mozilla should be no problem if it is correctly detected. Contact page is https://www.zurichbank.co.uk/homesuite/contactus.html
Status: UNCONFIRMED → NEW
Ever confirmed: true
https://secure.zurichbank.co.uk 'redirects' to https://secure.zurichbank.co.uk/cgi-bin/common/fortecgi?ServiceName=ZFSPortalHTTPAccessSO&TemplateName=vputpl/common/autologon.tmpl clearly it doesn't detect Gecko correctly, since Konqueror needs to masquerade, so presumably Mozilla trunk (2002082320 my build) would need to as well Netscape 7 pr 1 doesn't get detected properly either perhaps their faq refers to http://www not https://secure ?
can anyone test with mozilla identified as something else, see if everything works ? if so, this bug should be marked as [havefix], since that would mean they only need to sniff better...
my build today 2002082608 [GMT+1], with uabar added ua : Mozilla/4.78 [en] (X11; U; Linux 2.2.19 i686) site allows login etc Never really explored the site in anything else : )
Summary: Refuses to allow use by Gecko based browser → zurichbank.co.uk - Refuses to allow use by Gecko based browser
This won't matter in light of current news, Zurich is shedding its online banking
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
tech evang june 2003 reorg
Component: Europe: West → English Other
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.