netty5/handler/src/main/java/io/netty/handler/ipfilter
Norman Maurer ae0fbb45e4
Ensure the DefaultChannelHandlerContext is unlinked once removed (#9970)
Motivation:

At the moment the next / prev references are not set to "null" in the DefaultChannelHandlerContext once the ChannelHandler is removed. This is bad as it basically let users still use the ChannelHandlerContext of a ChannelHandler after it is removed and may produce very suprising behaviour.

Modifications:

- Fail if someone tries to use the ChannelHandlerContext once the ChannelHandler was removed (for outbound operations fail the promise, for inbound fire the error through the ChannelPipeline)
- Fix some handlers to ensure we not use the ChannelHandlerContext after the handler was removed
- Adjust DefaultChannelPipeline / DefaultChannelHandlerContext to fixes races with removal / replacement of handlers

Result:

Cleanup behaviour and make it more predictable for pipeline modifications
2020-03-01 08:13:33 +01:00
..
AbstractRemoteAddressFilter.java Ensure the DefaultChannelHandlerContext is unlinked once removed (#9970) 2020-03-01 08:13:33 +01:00
IpFilterRule.java
IpFilterRuleType.java
IpSubnetFilterRule.java migrate java8: use requireNonNull (#8840) 2019-02-04 10:32:25 +01:00
RuleBasedIpFilter.java migrate java8: use requireNonNull (#8840) 2019-02-04 10:32:25 +01:00
UniqueIpFilter.java migrate java8: use lambda and method reference (#8781) 2019-01-29 14:06:05 +01:00
package-info.java