ad27387646
Motivations The test SniHandlerTest#testSniWithApnHandler() does not actually involve SNI: given the client setup, the ClientHello in the form of hex strings is not actually written to the wire, so the server never receives that. We may need to write in somewhere else (e.g., channelActive()) instead of in initChannel() in order for the hex strings to reach the server. So here what's actually going on is an ordinary TLS C/S communication without SNI. Modifications The client part is modified to enable SNI by using an SslHandler with an SSLEngine created by io.netty.handler.ssl.SslContext#newEngine(), where the server hostname is specified. Also, more clauses are added to verify that the SNI is indeed successful. Results Now the test verifies that both SNI and APN actually happen and succeed. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-haproxy | ||
| codec-http | ||
| codec-socks | ||
| common | ||
| example | ||
| handler | ||
| license | ||
| microbench | ||
| tarball | ||
| testsuite | ||
| testsuite-osgi | ||
| transport | ||
| transport-native-epoll | ||
| transport-rxtx | ||
| transport-sctp | ||
| transport-udt | ||
| .fbprefs | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| pom.xml | ||
| README.md | ||
| run-example.sh | ||
Netty Project
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Links
How to build
For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.
You require the following to build Netty:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.
Branches to look
Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.