andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,367 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
71ca9355dc
Go to file
James Roper 71ca9355dc Send full response for unsupported websocket versions 
Motivation:

WebSocketServerHandshakerFactory.sendUnsupportedVersionResponse does not
send a LastHttpContent, nor does it flush, and it doesn't send a content
length.

Modifications:

Changed sendUnsupportedVersionResponse to send FullHttpResponse, to
writeAndFlush, and to set a content length of 0. Also added a test for
this method.

Result:

Upstream handlers will be able to determine the end of the response, the
response will actually get written to the client, and the client will be
able to determine the end of the response.
2015-07-17 11:13:06 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
buffer [#3896] Unpooled.copiedBuffer(ByteBuffer) and copiedBuffer(ByteBuffer...) is not thread-safe. 2015-07-07 08:38:07 +02:00
codec [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
codec-http Send full response for unsupported websocket versions 2015-07-17 11:13:06 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
common [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
example [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
handler Better handling of BUFFER_OVERFLOW when unwrap data. 2015-07-08 10:32:57 +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-06-23 11:08:27 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
transport Fix DatagramChannel javadoc 2015-07-12 20:20:28 +02:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-06-23 11:08:27 +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 to netty-tcnative 1.1.33.Fork4 2015-07-10 11:54:19 +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.