andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,760 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
74f418bace
Go to file
Daniel Bevenius 74f418bace Adding support for specifying preflight response headers. 
Motivation:

An intermediary like a load balancer might require that a Cross Origin
Resource Sharing (CORS) preflight request have certain headers set.
As a concrete example the Elastic Load Balancer (ELB) requires the
'Date' and 'Content-Length' header to be set or it will fail with a 502
error code.

This works is an enhancement of https://github.com/netty/netty/pull/2290

Modifications:

CorsConfig has been extended to make additional HTTP response headers
configurable for preflight responses. Since some headers, like the
'Date' header need to be generated each time, m0wfo suggested using a
Callable.

Result:

By default, the 'Date' and 'Content-Lenght' headers will be sent in a
preflight response. This can be overriden and users can specify
any headers that might be required by different intermediaries.
2014-03-21 15:40:59 +01:00
all Ensure native transport is included in all and tarball 2014-02-17 22:46:07 +01:00
buffer Implement Thread caches for pooled buffers to minimize conditions. This fixes [#2264] and [#808]. 2014-03-20 09:30:57 -07:00
codec Remove condition in ChannelHandlerAdapter.isSharable() by caching the result of the annotation lookup. 2014-03-12 12:31:52 +01:00
codec-http Adding support for specifying preflight response headers. 2014-03-21 15:40:59 +01:00
codec-memcache [codec-memcache] Simplify object hierachy and remove Headers. 2014-03-04 13:05:30 +01:00
codec-socks Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
common Use SecureRandom.generateSeed() to generate ThreadLocalRandom's initialSeedUniquifier 2014-03-21 13:43:15 +09:00
example Ensure the HttpResponseEncoder is always placed before the HttpObjectAggregator. Part of [#2219] 2014-03-05 06:58:04 +01:00
handler Replace usage of System.currentTimeMillis() with System.nanoTime() 2014-03-18 16:06:16 +09:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:28:37 +01:00
microbench Upgrade JMH to 0.4.1 and make use of @Params. 2014-02-23 16:39:39 +01:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Reduce SO_TIMEOUT of testsuite so it finishes sooner 2014-03-17 10:54:07 +09:00
transport Use the length of MAC address as the last property to compare to get the best MAC address 2014-03-21 12:58:58 +09:00
transport-native-epoll Perform cross-tests between NIO and epoll transport 2014-03-17 10:35:48 +09:00
transport-rxtx Apply receive timeout to commPort when using RxtxChannel. Part of [#1390] 2014-02-23 16:31:34 +01:00
transport-sctp Directly use memory addresses for gathering writes to reduce gc pressure. Part of [#2239] 2014-02-21 13:37:33 +01:00
transport-udt Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Format and partially describe Gitignore 2013-12-10 07:04:38 +01: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
NOTICE.txt [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:28:37 +01:00
pom.xml Add -verbose:gc option for test runs 2014-03-17 14:17:08 +09:00
README.md Update README.md 2014-01-16 14:38:36 +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.