Go to file
Scott Mitchell 6525240236 SPDY codec must check headers are lower case
Motivation:
The SPDY spec requires that all header names be lowercase (see https://www.chromium.org/spdy/spdy-protocol/spdy-protocol-draft3-1#TOC-3.2-HTTP-Request-Response). The SPDY codec header name validator does not enforce this requirement.

Modifications:
- SpdyCodecUtil.validateHeaderName should check for upper case characters and throw an error if any are found.

Result:
SPDY codec header validation enforces specification requirement.
2015-07-31 11:25:50 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
codec [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
codec-http SPDY codec must check headers are lower case 2015-07-31 11:25:50 -07:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
common (fix) typo 2015-07-30 12:50:36 +02:00
example [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
handler [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Microbench backport issue 2015-07-30 10:33:10 -07:00
tarball [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
transport Correctly count acquired channels when timeout occurs in FixedChannelPool 2015-07-30 07:56:08 +02:00
transport-native-epoll Add support for IP_FREEBIND when using native transport 2015-07-30 20:56:30 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02: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 [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09: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

The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.