andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,443 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
428c11ea59
Go to file
Scott Mitchell 428c11ea59 SpdyHttpHeaders are not lowercase 
Motivation:
According to the SPDY spec https://www.chromium.org/spdy/spdy-protocol/spdy-protocol-draft3-1#TOC-3.2.1-Request header names must be lowercase. Our predefined SPDY extension headers are not lowercase.

Modifications
- SpdyHttpHeaders should define header names in lower case

Result:
Compliant with SPDY spec, and header validation code does not detect errors for our own header names.
2015-09-16 11:38:52 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
codec [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
codec-http SpdyHttpHeaders are not lowercase 2015-09-16 11:38:52 -07:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
common [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
example [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
handler Support SSLSession.getLocalCertificates() and getLocalPrincipal() when using OpenSSL 2015-09-15 12:21:47 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
testsuite Correctly throw SSLPeerUnverifiedException if peers identity has not been verified 2015-09-15 09:57:32 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
transport Ensure close caused by write will happen before write promise is notified 2015-09-16 20:35:34 +02:00
transport-native-epoll [#4205] Correctly set EPOLLOUT flag whe writeBytes(...) was not able to write everything 2015-09-16 07:28:28 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-09-02 08:58:54 +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 Upgrade jzlib version 2015-09-15 08:30:15 +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

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 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.