-
Notifications
You must be signed in to change notification settings - Fork 1.1k
GH-8609: Fix bug that cannot applied correctly TcpConnectorInterceptor #8610
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
Conversation
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.
I wonder what is wrong with my suggestion to fix TcpConnectionInterceptorSupport
: #8609 (comment).
The test looks OK and I believe the outcome will be exactly the same with my fix.
The difference is wrapped connection that passed to interceptor's Your change is:
My change is:
I thought it would be better to pass the last wrapped connection to all interceptors, what do you think? |
Yeah... It would be better to not have any wrapping at all, but rather just a chain of interceptors injected into a Let's listener what @garyrussell has in his mind on the matter! Thank you for the contribution anyway! |
My intuition is that an interceptor in the chain should only reference the next in the chain, not the outermost one. So I prefer @artembilan 's approach. |
@garyrussell @artembilan |
…ectorInterceptor Fixes spring-projects#8609 * Changed to passed the self instance to addNewConnection instead of argument's connection
@garyrussell @artembilan |
... and cherry-picked to @kazuki43zoo , |
Fixes #8609
add getLastWrapper() in TcpConnectionSupportchange to passed the instance that geted via getLastWrapper() instead of self instance to TcpSender#addNewConnection