Go to file
Thomas Segismont 7f23c34b55 ReadOnlyHttp2Headers.contains always ignores case for values
Motivation:

When checking if a value is present, ReadOnlyHttp2Headers always ignores
case for values.

RFC 7540 says: https://tools.ietf.org/html/rfc7540#section-8.1.2
"header field names are strings of ASCII characters that are compared in a case-insensitive fashion"

But there is no such constraint on header values

Modifications:

Updated ReadOnlyHttp2Headers.contains to compare header value in a
case-sensitive way.

Result:

ReadOnlyHttp2Headers compares header names in a case-insensitive way,
values in a case-sensitive way.
2018-01-27 20:29:40 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
.mvn/wrapper Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
all [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
bom [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
buffer HttpResponseStatus object allocation reduction 2018-01-24 22:01:52 -08:00
codec Use FastThreadLocal for CodecOutputList 2018-01-23 11:34:28 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-http Fix HttpPostMultipartRequestDecoder.splitMultipartHeader() String index out of range: -1 with empty header 2018-01-25 14:03:35 +01:00
codec-http2 ReadOnlyHttp2Headers.contains always ignores case for values 2018-01-27 20:29:40 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-stomp Fix StompFrame.copy() does not copy headers 2018-01-26 08:30:12 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
common ObjectCleanerThread must be a deamon thread to ensure the JVM can always terminate. 2018-01-26 08:25:42 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
docker Provide a Docker image for reproducible builds 2018-01-22 20:02:17 +01:00
example [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
handler [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
license Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
microbench Use FastThreadLocal for CodecOutputList 2018-01-23 11:34:28 +01:00
resolver [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
resolver-dns Fix race-condition when using DnsCache in DnsNameResolver 2018-01-23 08:04:33 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport Reduce object allocation by using same ChannelFutureListener instance. 2018-01-26 08:42:39 +01:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-native-kqueue [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +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 Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02: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: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 Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
pom.xml Replace reflective access of Throwable#addSuppressed with version guarded access 2018-01-25 19:56:17 +01:00
README.md Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +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.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.