HeadContext is inbound and outbound (#8592)
Motivation: Our HeadContext in DefaultChannelPipeline does handle inbound and outbound but we only marked it as outbound. While this does not have any effect in the current code-base it can lead to problems when we change our internals (this is also how I found the bug). Modifications: Construct HeadContext so it is also marked as handling inbound. Result: More correct code.
This commit is contained in:
parent
e114d6be46
commit
5b239150f1
@ -1331,7 +1331,7 @@ public class DefaultChannelPipeline implements ChannelPipeline {
|
|||||||
private final Unsafe unsafe;
|
private final Unsafe unsafe;
|
||||||
|
|
||||||
HeadContext(DefaultChannelPipeline pipeline) {
|
HeadContext(DefaultChannelPipeline pipeline) {
|
||||||
super(pipeline, null, HEAD_NAME, false, true);
|
super(pipeline, null, HEAD_NAME, true, true);
|
||||||
unsafe = pipeline.channel().unsafe();
|
unsafe = pipeline.channel().unsafe();
|
||||||
setAddComplete();
|
setAddComplete();
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user