jetty-project/jetty-npn — pull request #5 by Scottmitch (2014-10-04 14:42:12+00:00)
Title: No common next protocol should fail handshake

Motiviation:
There is currently no means to fail the SSL handshake due to there being no common next protocol.
The current treatment of a return value from also results in no NextProtocolMessage being sent to the server.
According to [NPN RFC section 3](http://tools.ietf.org/html/draft-agl-tls-nextprotoneg-04#section-3) and [Google's NPN Spec, Next Protocol Negotiation Extension Section](https://technotes.googlecode.com/git/nextprotoneg.html) if the server included a extension.

Modifications:
-Returning from should result in a failed SSL handshake with alert no_application_protocol(120)
-Add unit test for this scenario

Result:
jetty npn-boot is compatible with specifications and allows a means to fail the handshake if no common next procotols found.