-
Notifications
You must be signed in to change notification settings - Fork 344
Fix Netty 4.1 HTTP/1.1 pipelined response tracing #11937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ygree
wants to merge
3
commits into
master
Choose a base branch
from
ygree/fix-netty41-http11-pipelining-context-queue
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
28 changes: 28 additions & 0 deletions
28
...tty-4.1/src/test/java/datadog/trace/instrumentation/netty41/ServerRequestContextTest.java
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| package datadog.trace.instrumentation.netty41; | ||
|
|
||
| import static org.junit.jupiter.api.Assertions.assertFalse; | ||
| import static org.junit.jupiter.api.Assertions.assertNotNull; | ||
| import static org.junit.jupiter.api.Assertions.assertNull; | ||
|
|
||
| import datadog.context.Context; | ||
| import io.netty.handler.codec.http.DefaultHttpHeaders; | ||
| import io.netty.util.DefaultAttributeMap; | ||
| import org.junit.jupiter.api.Test; | ||
|
|
||
| class ServerRequestContextTest { | ||
| private static final int PIPELINING_LIMIT = 1000; | ||
|
|
||
| @Test | ||
| void disablesTrackingWhenPipeliningLimitIsExceeded() { | ||
| DefaultAttributeMap attributes = new DefaultAttributeMap(); | ||
|
|
||
| for (int i = 0; i < PIPELINING_LIMIT; i++) { | ||
| assertNotNull(ServerRequestContext.add(attributes, Context.root(), new DefaultHttpHeaders())); | ||
| } | ||
|
|
||
| assertFalse(ServerRequestContext.canTrackRequest(attributes)); | ||
| assertNull(ServerRequestContext.nextResponse(attributes)); | ||
| assertNull(attributes.attr(AttributeKeys.CONTEXT_ATTRIBUTE_KEY).get()); | ||
| assertNull(ServerRequestContext.add(attributes, Context.root(), new DefaultHttpHeaders())); | ||
| } | ||
| } |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When AppSec blocks a streaming response, this state now lives only on the head
ServerRequestContext; the replacement blockingFullHttpResponseis written throughHttpServerResponseTracingHandler, which immediately removes that context while the channel close is still asynchronous. Any subsequent original response chunks written before the close then see no blocked context (or the next pipelined request's context) and are forwarded instead of being released, regressing the previous channel-level blocked flag behavior for non-FullHttpResponseresponses.Useful? React with 👍 / 👎.