Norman Maurer
0db2901f4d
[maven-release-plugin] prepare for next development iteration
2017-05-11 16:00:55 +02:00
Norman Maurer
f7a19d330c
[maven-release-plugin] prepare release netty-4.1.11.Final
2017-05-11 16:00:16 +02:00
Norman Maurer
6915ec3bb9
[maven-release-plugin] prepare for next development iteration
2017-04-29 14:10:00 +02:00
Norman Maurer
f30f242fee
[maven-release-plugin] prepare release netty-4.1.10.Final
2017-04-29 14:09:32 +02:00
Nikolay Fedorovskikh
0692bf1b6a
fix the typos
2017-04-20 04:56:09 +02:00
Norman Maurer
2b8c8e0805
[maven-release-plugin] prepare for next development iteration
2017-03-10 07:46:17 +01:00
Norman Maurer
1db58ea980
[maven-release-plugin] prepare release netty-4.1.9.Final
2017-03-10 07:45:28 +01:00
Norman Maurer
735d6dd636
[maven-release-plugin] prepare for next development iteration
2017-01-30 15:14:02 +01:00
Norman Maurer
76e22e63f3
[maven-release-plugin] prepare release netty-4.1.8.Final
2017-01-30 15:12:36 +01:00
Norman Maurer
7f01da8d0f
[maven-release-plugin] prepare for next development iteration
2017-01-12 11:36:51 +01:00
Norman Maurer
7a21eb1178
[maven-release-plugin] prepare release netty-4.1.7.Final
2017-01-12 11:35:58 +01:00
Norman Maurer
5f533b7358
[maven-release-plugin] prepare for next development iteration
2016-10-14 13:20:41 +02:00
Norman Maurer
35fb0babe2
[maven-release-plugin] prepare release netty-4.1.6.Final
2016-10-14 12:47:19 +02:00
Dominik Obermaier
5bb677e7c2
This PR fixes an issue with the PROXY protocol where the reader index of a consumed byte array was not set correctly.
...
Motivation:
When using the AF_UNIX PROXY protocol, the reader index was not set correctly after consuming the message bytes of the original header ByteBuf. This caused no immediate harm because after the codepath there is no consumer of the ByteBuf in the current implementation. It’s a bug nevertheless, because consumers of the ByteBuf for extensions (like TLVs, which are allowed by the PROXY protocol spec) would consume a ByteBuf that has a wrong readerIndex when using AF_UNIX instead of e.g. IPv4 (which has correct behaviour)
Modifications:
Increase the reader index of the ByteBuf after it was read
Result:
Correct and consistent behaviour of the AF_UNIX codepath
2016-09-29 21:21:01 +02:00
Norman Maurer
54b1a100f4
[maven-release-plugin] prepare for next development iteration
2016-08-26 10:06:32 +02:00
Norman Maurer
1208b90f57
[maven-release-plugin] prepare release netty-4.1.5.Final
2016-08-26 04:59:35 +02:00
Dmitriy Dumanskiy
a80ea46b8e
Removed custom split method as it is not effective anymore.
2016-08-01 21:49:33 +02:00
Norman Maurer
cb7cf4491c
[maven-release-plugin] prepare for next development iteration
2016-07-27 13:29:56 +02:00
Norman Maurer
9466b32d05
[maven-release-plugin] prepare release netty-4.1.4.Final
2016-07-27 13:16:59 +02:00
Norman Maurer
047f6aed28
[maven-release-plugin] prepare for next development iteration
2016-07-15 09:09:13 +02:00
Norman Maurer
b2adea87a0
[maven-release-plugin] prepare release netty-4.1.3.Final
2016-07-15 09:08:53 +02:00
Norman Maurer
4676a2271c
[maven-release-plugin] prepare for next development iteration
2016-07-01 10:33:32 +02:00
Norman Maurer
ad270c02b9
[maven-release-plugin] prepare release netty-4.1.2.Final
2016-07-01 09:07:40 +02:00
Norman Maurer
4dec7f11b7
[maven-release-plugin] prepare for next development iteration
2016-06-07 18:52:34 +02:00
Norman Maurer
cf670fab75
[maven-release-plugin] prepare release netty-4.1.1.Final
2016-06-07 18:52:22 +02:00
Norman Maurer
6ca49d1336
[maven-release-plugin] prepare for next development iteration
2016-05-25 19:16:44 +02:00
Norman Maurer
446b38db52
[maven-release-plugin] prepare release netty-4.1.0.Final
2016-05-25 19:14:15 +02:00
Norman Maurer
572bdfb494
[maven-release-plugin] prepare for next development iteration
2016-04-10 08:37:18 +02:00
Norman Maurer
c6121a6f49
[maven-release-plugin] prepare release netty-4.1.0.CR7
2016-04-10 08:36:56 +02:00
Norman Maurer
6e919f70f8
[maven-release-plugin] rollback the release of netty-4.1.0.CR7
2016-04-09 22:13:44 +02:00
Norman Maurer
4cdd51509a
[maven-release-plugin] prepare release netty-4.1.0.CR7
2016-04-09 22:05:34 +02:00
Trustin Lee
3b941c2a7c
[maven-release-plugin] prepare for next development iteration
2016-04-02 01:25:05 -04:00
Trustin Lee
7368ccc539
[maven-release-plugin] prepare release netty-4.1.0.CR6
2016-04-02 01:24:55 -04:00
Norman Maurer
cee38ed2b6
[maven-release-plugin] prepare for next development iteration
2016-03-29 16:45:13 +02:00
Norman Maurer
9cd9e7daeb
[maven-release-plugin] prepare release netty-4.1.0.CR5
2016-03-29 16:44:33 +02:00
Norman Maurer
28d03adbfe
[maven-release-plugin] prepare for next development iteration
2016-03-21 11:51:50 +01:00
Norman Maurer
4653dc1d05
[maven-release-plugin] prepare release netty-4.1.0.CR4
2016-03-21 11:51:12 +01:00
Norman Maurer
ca443e42e0
[maven-release-plugin] prepare for next development iteration
2016-02-19 23:00:11 +01:00
Norman Maurer
f39eb9a6b2
[maven-release-plugin] prepare release netty-4.1.0.CR3
2016-02-19 22:59:52 +01:00
Norman Maurer
75a2ddd61c
[maven-release-plugin] prepare for next development iteration
2016-02-04 16:51:44 +01:00
Norman Maurer
7eb3a60dba
[maven-release-plugin] prepare release netty-4.1.0.CR2
2016-02-04 16:37:06 +01:00
Norman Maurer
1c417e5f82
[maven-release-plugin] prepare for next development iteration
2016-01-21 15:35:55 +01:00
Norman Maurer
c681a40a78
[maven-release-plugin] prepare release netty-4.1.0.CR1
2016-01-21 15:28:21 +01:00
Norman Maurer
2ecce8fa56
[maven-release-plugin] prepare for next development iteration
2015-11-10 22:59:33 +01:00
Norman Maurer
6a93f331d3
[maven-release-plugin] prepare release netty-4.1.0.Beta8
2015-11-10 22:50:57 +01:00
Norman Maurer
2ff2806ada
[maven-release-plugin] prepare for next development iteration
2015-10-02 09:03:29 +02:00
Norman Maurer
5a43de10f7
[maven-release-plugin] prepare release netty-4.1.0.Beta7
2015-10-02 09:02:58 +02:00
Norman Maurer
34de2667c7
[maven-release-plugin] prepare for next development iteration
2015-09-02 11:45:20 +02:00
Norman Maurer
2eb444ec1d
[maven-release-plugin] prepare release netty-4.1.0.Beta6
2015-09-02 11:36:11 +02:00
Norman Maurer
c53dbb748e
Add ProtocolDetectionResult and use it in HAProxyMessageDecoder for allow detect HAProxy protocol.
...
Motivation:
Sometimes it is useful to detect if a ByteBuf contains a HAProxy header, for example if you want to write something like the PortUnification example.
Modifications:
- Add ProtocolDetectionResult which can be used as a return type for detecting different protocol.
- Add new method which allows to detect HA Proxy messages.
Result:
Easier to detect protocol.
2015-06-23 08:59:07 +02:00
