andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,583 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
27118ec53a
Go to file
Norman Maurer 27118ec53a Correctly handle non handshake commands when using SniHandler 
Motivation:

As we can only handle handshake commands to parse SNI we should try to skip alert and change cipher spec commands a few times before we fallback to use a default SslContext.

Modifications:

- Use default SslContext if no application data command was received
- Use default SslContext if after 4 commands we not received a handshake command
- Simplify code
- Eliminate multiple volatile fields
- Rename SslConstants to SslUtils
- Share code between SslHandler and SniHandler by moving stuff to SslUtils

Result:

Correct handling of non handshake commands and cleaner code.
2016-01-14 20:46:04 +01:00
all Fix version 2015-11-24 21:24:22 +01:00
buffer Fix IndexOutOfBoundsException for CompositeByteBuf #4679 2016-01-08 19:13:32 -08:00
codec [#4635] Stop decoding if decoder was removed 2016-01-05 11:07:50 +01:00
codec-haproxy Fix version 2015-11-24 21:24:22 +01:00
codec-http Fix InternalAttribute.equals 2016-01-11 09:25:54 +01:00
codec-socks Fix version 2015-11-24 21:24:22 +01:00
common Fix PlatformDependent.newAtomic*FieldUpdater type safety 2016-01-08 08:51:44 +01:00
example Use jetty-alpn-agent to simplify pom.xml 2016-01-04 20:40:46 +01:00
handler Correctly handle non handshake commands when using SniHandler 2016-01-14 20:46:04 +01:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Fix version 2015-11-24 21:24:22 +01:00
tarball Fix version 2015-11-24 21:24:22 +01:00
testsuite Fix version 2015-11-24 21:24:22 +01:00
testsuite-osgi Fix version 2015-11-24 21:24:22 +01:00
transport Allow to change if EmbeddedChannel should handle close() and disconnect() different. 2016-01-14 07:30:08 +01:00
transport-native-epoll [#4658] Fix encoding of pom.xml file 2016-01-06 08:12:15 +01:00
transport-rxtx Fix version 2015-11-24 21:24:22 +01:00
transport-sctp Improve SctpMessage.hashCode method 2016-01-05 20:45:43 +01:00
transport-udt Fix version 2015-11-24 21:24:22 +01:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:37:12 +09:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Fix deprecated Maven expressions usage 2016-01-08 14:38:54 +01:00
README.md Fix the 'branches to look' section 2015-10-27 13:58:06 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09:00

README.md

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:

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

The 'master' branch is where the development of the latest major version lives on. The development of all other 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.