Scott Mitchell f8af84d599 ALPN should allow handshake failure if no compatible protocols found ... Motivation: If there are no common protocols in the ALPN protocol exchange we still compete the handshake successfully. This handshake should fail according to http://tools.ietf.org/html/rfc7301#section-3.2 with a status of no_application_protocol. The specification also allows for the server to "play dumb" and not advertise that it supports ALPN in this case (see MAY clauses in http://tools.ietf.org/html/rfc7301#section-3.1) Modifications: -Upstream project used for ALPN (alpn-boot) does not support this. So a PR https://github.com/jetty-project/jetty-alpn/pull/3 was submitted. -The netty code using alpn-boot should support the new interface (return null on existing method). -Version number of alpn-boot must be updated in pom.xml files Result: -Netty fails the SSL handshake if ALPN is used and there are no common protocols.		2014-10-30 19:39:31 -04:00
..
src/main	ALPN should allow handshake failure if no compatible protocols found	2014-10-30 19:39:31 -04:00
.gitignore	[#844] [#867] Add UDT transport	2013-01-07 21:06:22 +01:00
pom.xml	Add proxy support for client socket connections	2014-10-14 12:40:33 +09:00