Closed
Bug 182026
Opened 23 years ago
Closed 22 years ago
java app fails with jre 1.4.0 / 1.4.1 but ok with jre 1.3.1
Categories
(Core Graveyard :: Java: OJI, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ste_ve, Assigned: joshua.xia)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2) Gecko/20021114
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2) Gecko/20021114
co-operative bank internet banking application fails with Sun's jre 1.4.1 or
1.4.0 WORKS OK with jre 1.3.1.
Error message is javax.net.ssl.SSLException: SSL V2.0 servers are not supported
Reproducible: Always
Steps to Reproduce:
1.run the above url which loads new window, loads java and application
2.
3.
Actual Results:
java console shows javax.net.ssl.SSLException: SSL V2.0 servers are not supported
Expected Results:
initialise applet with no errors as in jre 1.3.1
Comment 1•23 years ago
|
||
Confirming bug - 5 hours old cvs based build - JRE 1.4.1_01 - WinXP-Sp1.
Comment 3•23 years ago
|
||
very clear error message :
SSL V2.0 servers are not supported
(they might be suppoorted in JRE1.3)
-> invalid
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 4•23 years ago
|
||
don't think it's as simple as that see
http://forum.java.sun.com/thread.jsp?thread=4257&forum=2&message=697848
and security preferences has radio buttons for SSL v2, V3 and TLS
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 5•23 years ago
|
||
*** Bug 182780 has been marked as a duplicate of this bug. ***
Comment 6•23 years ago
|
||
*** Bug 184486 has been marked as a duplicate of this bug. ***
Comment 7•23 years ago
|
||
Shall we move then to Tech Evangelism and ask site to remove move to SSLv3 ?
Then, let's also mark bug 100373 dupe of this one then...
Otherwise, is JRE 1.4.2 beta support this ? Someone from Sun ?
*** Bug 191444 has been marked as a duplicate of this bug. ***
| Reporter | ||
Comment 10•23 years ago
|
||
Don't see this as a browser problem per se, more of a Java issue as some people
saying that they get this error with SSL v3 and 40 bit encryption (see link on
earlier post).
So I don't see what use it will be on Tech Evangelism except maybe to bury this
bug.
Maybe it's not specifically a browser issue but a Sun problem. Although there
have been Java / Mozilla problems in the past, this seems to be JRE issue.
I think that the status should be changed from unconfirmed as it is real enough
(or we wouldn't be getting dupes for ecample). I thnk that a data capture of
the two different versions of Java would be interesting to a Java / SSL
developer - anyone interested?
Comment 11•23 years ago
|
||
I can't tell whether this is really a browser problem but my experience is that
both IE (5.x and 6) and Opera 7.1 handle the same pages without crashing or
causing CPU runaway.
Comment 12•22 years ago
|
||
URL no longer valid? Co-op bank have ditched the Java in favour of an HTML service.
Comment 13•22 years ago
|
||
-> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 22 years ago
Resolution: --- → WORKSFORME
Comment 14•21 years ago
|
||
This bug should be re-opened, currently the acumen system (co-op's html+js
business banking web app) does not support Gecko browsers, and their Java
fallback for "non-IE6 browsers" doesn't work for me in Firefox (FF1.0.4 WinXP
Pro SP2 JRE 1.5).
Acumen: http://www.co-operativebank.co.uk/cgi-bin/Launch_cashplus.cgi?banking
Java app: http://apps.co-operativebank.co.uk/cgi-bin/Launch_corporate.cgi?cust
To clarify, it appears there is currently no way for FF users to use the co-op
online business banking, bar using a different browser.
I have spoken to co-op tech support repeatedly and they have specified that they
are working on supporting gecko-based browsers but they do not have a time-scale
on when this will be available.
I recommend either re-opening this bug and changing the summary, platform and
adding evangelism keyword or creating a new bug. I would do this myself, but I
don't yet have privs to do so.
You need to log in
before you can comment on or make changes to this bug.
Description
•