andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,909 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
f402350d76
Go to file
Frederic Bregier f402350d76 [#2544] Correctly parse Multipart-mixed POST HTTP request in case of entity ends with odd number of 0x0D 
Motivation:
When an attribute is ending with an odd number of CR (0x0D), the decoder
add an extra CR in the decoded attribute and should not.

Modifications:
Each time a CR is detected, the next byte was tested to be LF or not. If
not, in a number of places, the CR byte was lost while it should not be.
When a CR is detected, if the next byte is not LF, the CR byte should be
saved as the position point to the next byte (not LF). When a CR is
detected, if there is not yet other available bytes, the position is
reset to the position of CR (since a LF could follow).

A new Junit test case is added, using DECODER and variable number of CR
in the final attribute (testMultipartCodecWithCRasEndOfAttribute).

Result:
The attribute is now correctly decoded with the right number of CR
ending bytes.
2014-06-08 11:24:18 +02:00
all Initial STOMP protocol work from @sskachkov 2014-06-04 17:09:42 +09:00
buffer [#2436] Unsafe*ByteBuf implementation should only invert bytes if ByteOrder differ from native ByteOrder 2014-06-05 10:59:22 +02:00
codec Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
codec-http [#2544] Correctly parse Multipart-mixed POST HTTP request in case of entity ends with odd number of 0x0D 2014-06-08 11:24:18 +02:00
codec-memcache Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
codec-socks Clean up the examples 2014-05-23 17:13:09 +09:00
codec-stomp Fix StompSubframeEncoderTest failure 2014-06-05 17:04:58 +09:00
common Clean up MpscLinkedQueue, fix its leak, and make it work without Unsafe 2014-06-04 03:23:55 +09:00
example Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
handler [#2494] Fix data curruption by ChannelTrafficShapingHandler 2014-06-03 08:38:05 +02:00
license Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:30 +09:00
microbench [#2436] Unsafe*ByteBuf implementation should only invert bytes if ByteOrder differ from native ByteOrder 2014-06-05 10:59:22 +02:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
transport ChannelFlushPromiseNotifier should allow long value for pendingDataSize 2014-06-03 17:34:53 +02:00
transport-native-epoll Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:06 +09:00
transport-rxtx Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-sctp Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-udt Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09: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 Add JVM crash logs to .gitignore 2014-05-18 21:36:54 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:30 +09:00
pom.xml Initial STOMP protocol work from @sskachkov 2014-06-04 17:09:42 +09:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:42 +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 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.