Scott Mitchell 449befa003 Workaround IBM's J9 JVM getSupportedCipherSuites() returning SSL_ prefix cipher names ... Motivation: IBM's J9 JVM utilizes a custom cipher naming scheme with SSL_ prefix [1] instead of the TLS_ prefix defined by TLS RFCs and the JSSE cihper suite names [2]. IBM's documentation says that the SSL_ prefix are "interchangeable" with cipher names with the TLS_ prefix [1]. To work around this issue we parse the supported cipher list and see an SSL_ prefix we can also add the same cipher with the TLS_ prefix. For more details see a discussion on IBM's forums [3] and IBM's issue tracker [4]. [1] https://www.ibm.com/support/knowledgecenter/en/SSYKE2_8.0.0/com.ibm.java.security.component.80.doc/security-component/jsse2Docs/ciphersuites.html [2] http://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#ciphersuites [3] https://www.ibm.com/developerworks/community/forums/html/topic?id=9b5a56a9-fa46-4031-b33b-df91e28d77c2 [4] https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=71770 Modifications: - When parsing the supported cipher list to get the supported ciphers and we encounter a SSL_ prefix we should also add a TLS_ prefix cipher. - Remove SSL_ prefix ciphers from Http2SecurityUtil. Result: Work around for IBM JVM's custom naming scheme covers more cases for supported cipher suites.		2017-07-05 09:05:42 -04:00
..
main/java/io/netty/handler/codec/http2	Workaround IBM's J9 JVM getSupportedCipherSuites() returning SSL_ prefix cipher names	2017-07-05 09:05:42 -04:00
test	DefaultHttp2ConnectionEncoder#writeHeaders shouldn't send GO_AWAY if stream is closed	2017-06-28 12:06:00 -04:00