appsec: never start a new WAF Context when one is in context #2989
+117
−26
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.
What does this PR do?
This PR does two things:
FindOperation
function in dyngowaf.ContextOperation
in the current context so we don't start more than one at a timeMotivation
For example
gorilla/mux
andgo-chi/chi
are contribs that usesnet/http
under the hood and since orchestrion will be instrumenting both of them, we will have multiple WAF Contexts in the Operation startMicrobenchmarks
Reviewer's Checklist
Unsure? Have a question? Request a review!