Go to file
Cory Benfield 14154074f2 Don't loop over TLS records for SNI (#7479)
Motivation:

The AbstractSniHandler previously was willing to tolerate up to three
non-handshake records before a ClientHello that contained an SNI
extension field. This is, so far as I can tell, completely
unnecessary: no TLS implementation will be sending alerts or change
cipher spec messages before ClientHello.

Given that it was not possible to determine why this loop is in
the code to begin with, it's probably just best to remove it.

Modifications:

Remove the for loop.

Result:

The AbstractSniHandler will more rapidly determine whether it should
pass the records on to the default SSL handler.

Co-authored-by: Norman Maurer <norman_maurer@apple.com>
2019-07-01 11:22:55 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
.mvn support publishing snapshots from docker based ci (#8634) 2018-12-07 05:43:06 +01:00
all [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
bom [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
buffer Fix the issue of incorrectly calculating the number of dump lines when using PrettyDump in ByteBufUtil (#9304) 2019-07-01 08:35:18 +02:00
codec optimize some code (#9289) 2019-06-28 13:48:23 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
codec-http [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
codec-http2 Http2FrameCodecBuilder.autoAckSettingsFrame(...) must be public (#9295) 2019-06-29 09:23:38 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
codec-smtp optimize some code (#9289) 2019-06-28 13:48:23 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
common optimize some code (#9289) 2019-06-28 13:48:23 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
docker Remove deprecated GraalVM native-image flags (#9118) 2019-05-22 19:20:54 +02:00
example [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
handler Don't loop over TLS records for SNI (#7479) 2019-07-01 11:22:55 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
license Updated jboss-marshalling dependency to current license (#9172) 2019-05-23 07:21:11 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
resolver [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
testsuite-native-image [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
testsuite-shading [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
transport Ensure sc.close() is executed before FixedChannelPoolTest.testCloseAsync() returns (#9298) 2019-06-29 09:21:11 +02:00
transport-native-epoll Unconditionally initialize sockaddrs in epoll linuxsocket (#9299) 2019-06-29 12:16:58 +02:00
transport-native-kqueue [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitattributes Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
.gitignore Add .gitignore for docker-sync stuff 2019-03-19 14:03:15 +01:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
mvnw Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
mvnw.cmd Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
NOTICE.txt Updated jboss-marshalling dependency to current license (#9172) 2019-05-23 07:21:11 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2019-06-28 05:57:21 +00:00
README.md Provide an Automatic-Module-Name for the netty-all artifact fixes #7644 2018-01-27 20:31:16 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

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

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.

Usage with JDK 9

Netty can be used in modular JDK9 applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.all
  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.