-
Bug
-
Resolution: Fixed
-
P4
-
11
-
b11
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8268413 | 16u-cpu | Evan Whelan | P4 | Resolved | Fixed | master |
JDK-8268252 | 16.0.2 | Evan Whelan | P4 | Resolved | Fixed | b07 |
JDK-8273996 | 15.0.5 | Yuri Nesterenko | P4 | Resolved | Fixed | b02 |
JDK-8271390 | 11.0.14-oracle | Evan Whelan | P4 | Resolved | Fixed | b01 |
JDK-8273731 | 11.0.14 | Martin Doerr | P4 | Resolved | Fixed | b01 |
JDK-8271391 | 8u441 | Nibedita Jena | P4 | Resolved | Fixed | b01 |
javax.net.ssl|DEBUG|0F|Thread-1|2018-09-26 15:01:02.816 IST|SSLEngineOutputRecord.java:507|WRITE: TLS12 handshake, length = 155
For input records we have a '.' in the protocol version name. TLSv1.2 versus TLS12. Ideally, we should be consistent with protocol version naming in debug output.
- backported by
-
JDK-8268252 Inconsistent TLS protocol version in debug output
-
- Resolved
-
-
JDK-8268413 Inconsistent TLS protocol version in debug output
-
- Resolved
-
-
JDK-8271390 Inconsistent TLS protocol version in debug output
-
- Resolved
-
-
JDK-8271391 Inconsistent TLS protocol version in debug output
-
- Resolved
-
-
JDK-8273731 Inconsistent TLS protocol version in debug output
-
- Resolved
-
-
JDK-8273996 Inconsistent TLS protocol version in debug output
-
- Resolved
-
- relates to
-
JDK-8262438 sun/security/ssl/SSLLogger/LoggingFormatConsistency.java failed with "SocketException: Socket is closed"
-
- Resolved
-
- links to
-
Commit openjdk/jdk11u-dev/124f3aca
-
Commit openjdk/jdk15u-dev/3d7d0cf0
-
Commit openjdk/jdk16u/7616b2c0
-
Commit openjdk/jdk/a8672885
-
Review openjdk/jdk11u-dev/332
-
Review openjdk/jdk15u-dev/104
-
Review openjdk/jdk16u/126
-
Review openjdk/jdk/2331