JDK-8169362 : Interop automated testing with Chrome
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: javax.net.ssl
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-11-08
  • Updated: 2023-11-29
  • Resolved: 2016-11-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b145Fixed
Related Reports
Duplicate :  
JDK-8167547 - Test that unsupported EC curves should not be selected during TLS handshaking
Relates :  
JDK-8169361 - Interop automated testing for TLS implementation
Description
Add interop automated tests with Chrome browser.
Comments
URL: http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/60d4214cc8ba User: lana Date: 2016-11-16 20:23:22 +0000
16-11-2016
URL: http://hg.openjdk.java.net/jdk9/dev/jdk/rev/60d4214cc8ba User: xuelei Date: 2016-11-10 09:00:14 +0000
10-11-2016
This test case captures an initial ClientHello message from Chrome browser (version 54.0.2840.87 m (64-bit)) on Windows 10.), and check whether JDK can read and response to the ClientHello request. Similar test cases may be considered for other major releases of Chrome browsers, and other TLS vendors and browsers. For new test case, please file a new RFE and link it to JDK-8169361 so that we can have a recap about the interop testing coverage. See the ClientHelloInterOp.java and ClientHelloChromeInterOp.java for more details about how to code the test case. Normally, only need to copy ClientHelloChromeInterOp.java and update the ClientHelloMsg class field with the new captured one. Please consider to override the ClientHelloInterOp methods if needed for new test cases.
10-11-2016