-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
filter: clarify comment #13678
filter: clarify comment #13678
Conversation
The comment currently states that after returning FilterHeadersStatus::StopIteration, decodeData() or encodeData() might still be called which isn't possible since the filter chain is stopped. The only way to unblock the the chain is via continueDecoding() or continueEncoding() from some callback. Signed-off-by: Raul Gutierrez Segales <[email protected]>
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.
Thanks! I wonder if this was a copy paste snafu from FilterDataStatus's comments. 😮
Could you check spelling please?
/wait
Signed-off-by: Raul Gutierrez Segales <[email protected]>
ah, it was clang-format not spelling. updated -- thanks! |
The macos failure is not format nor spelling, seems transient. |
/retest |
Retrying Azure Pipelines. |
This reverts commit 2ab7c30. Signed-off-by: Raul Gutierrez Segales <[email protected]>
This reverts commit b4ba91f. Signed-off-by: Raul Gutierrez Segales <[email protected]>
* note that StopIteration refers only to header processing (data/body processing still moves forward) * however, if a local reply is sent than StopIteration stops headers/data/trailers for all filters Signed-off-by: Raul Gutierrez Segales <[email protected]>
Signed-off-by: Raul Gutierrez Segales <[email protected]>
Signed-off-by: Raul Gutierrez Segales <[email protected]>
Follow-up to envoyproxy#13678. Signed-off-by: Raul Gutierrez Segales <[email protected]>
Follow-up to #13678. Signed-off-by: Raul Gutierrez Segales <[email protected]>
The comment currently states that after returning
FilterHeadersStatus::StopIteration, decodeData() or encodeData() might
still be called which isn't possible since the filter chain is stopped.
The only way to unblock the chain is via continueDecoding() or
continueEncoding() from some callback.
Signed-off-by: Raul Gutierrez Segales [email protected]