-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: None
-
Component/s: security-libs
-
b123
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8239031 | openjdk8u252 | Bradford Wetmore | P2 | Resolved | Fixed | b03 |
| JDK-8235806 | 8u251 | Bradford Wetmore | P2 | Closed | Fixed | b01 |
| JDK-8239693 | emb-8u251 | Bradford Wetmore | P2 | Resolved | Fixed | team |
This works:
sslp.setApplicationProtocols(serverAPs);
sslSocket.setSSLParameters(sslp);
This does not:
sslp.setApplicationProtocols(serverAPs);
sslServerSocket.setSSLParameters(sslp);
When a SSLServerSocketImpl accept()s a connection, it doesn't pass applicationProtocols to the new SSLSocketImpl.
sslp.setApplicationProtocols(serverAPs);
sslSocket.setSSLParameters(sslp);
This does not:
sslp.setApplicationProtocols(serverAPs);
sslServerSocket.setSSLParameters(sslp);
When a SSLServerSocketImpl accept()s a connection, it doesn't pass applicationProtocols to the new SSLSocketImpl.
- backported by
-
JDK-8239031 ALPN not working when values are set directly on a SSLServerSocket
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-