bea5d0321a
Motivation: The proxy protocol provides client connection information for proxied network services. Several implementations exist (e.g. Haproxy, Stunnel, Stud, Postfix), but the primary motivation for this implementation is to support the proxy protocol feature of Amazon Web Services Elastic Load Balancing. Modifications: This commit adds a proxy protocol decoder for proxy protocol version 1 as specified at: http://haproxy.1wt.eu/download/1.5/doc/proxy-protocol.txt The foundation for version 2 support is also in this commit but it is explicitly NOT supported due to a lack of external implementations to test against. Result: The proxy protocol decoder can be used to send client connection information to inbound handlers in a channel pipeline from services which support the proxy protocol. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-dns | ||
| codec-http | ||
| codec-http2 | ||
| codec-memcache | ||
| codec-socks | ||
| codec-stomp | ||
| common | ||
| example | ||
| handler | ||
| license | ||
| microbench | ||
| tarball | ||
| testsuite | ||
| transport | ||
| transport-native-epoll | ||
| transport-rxtx | ||
| transport-sctp | ||
| transport-udt | ||
| .fbfilter.xml | ||
| .fbprefs | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| pom.xml | ||
| README.md | ||
| run-example.sh | ||
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
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.