andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
8,180 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
6a8532acd1
Go to file
Michael O'Brien 6a8532acd1 Reset the contentExpected flag when RSET is written 
Motivation:

If the remote server returns a 4xx/5xx error in response to
a DATA command (or earlier command if using pipelining),
SmtpRequestEncoder can become stuck in an invalid state,
not allowing any requests to be sent.

This makes the channel unusable and the connection has to be closed,
or the encoder handler has to be replaced.

Modifications:

If a RSET command is written to the channel, the contentExpected
flag is set to false, and the RSET is written to the channel.

Result:

Sending a RSET command after a server 4xx/5xx error will make it
possible to use the current connection for new mail transactions.
2017-05-19 19:36:04 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all Add uber-staging and uber-snapshot profile that can be used to generate uber all jars. 2017-05-16 08:28:23 +02:00
bom Correctly include native modules 2017-05-18 07:03:28 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-http Make HttpHeadersEncoder.encodeHeader package private to match class visibility. 2017-05-19 11:17:31 +02:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-smtp Reset the contentExpected flag when RSET is written 2017-05-19 19:36:04 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
common Share code that is needed to support shaded native libraries. 2017-05-19 19:33:21 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
handler SslHandler#handlerRemoved0() shouldn't care about the SSLEngine being a specific type but only if it's ReferenceCounted 2017-05-19 19:31:51 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Optimizations in NetUtil 2017-05-18 16:42:22 -07:00
resolver [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
resolver-dns UnixResolverDnsServerAddressStreamProvider default name server selection and ordering bug 2017-05-18 15:14:58 -07:00
tarball Add uber-staging and uber-snapshot profile that can be used to generate uber all jars. 2017-05-16 08:28:23 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
transport [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
transport-native-epoll Share code that is needed to support shaded native libraries. 2017-05-19 19:33:21 +02:00
transport-native-kqueue Add support to wrap an existing filedescriptor when using native kqueue transport 2017-05-19 19:34:47 +02:00
transport-native-unix-common KQueueSocket#setTrafficClass exceptions 2017-05-18 11:26:27 -07:00
transport-native-unix-common-tests KQueueSocket#setTrafficClass exceptions 2017-05-18 11:26:27 -07:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02: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 Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml Add uber-staging and uber-snapshot profile that can be used to generate uber all jars. 2017-05-16 08:28:23 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02: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

Development of all 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.