-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Connection leaks in Zuul "post" filters #1196
Conversation
@dsyer @spencergibb I wonder if I should move fix to either |
I get why you want to do this, but is there any proof that it's necessary? Something that is obviously broken without it? Otherwise I'm wondering whether maybe Netflix code covers this scenario already somewhere. P.S. you probably need to rebase your branch and re-push to clean up the history. |
d926c9b
to
deaf62e
Compare
…re SendResponseFilter being executed.
deaf62e
to
ddd57b3
Compare
@dsyer Zuul advocates writing custom filters and I assume a lot of people do it. In my case I have custom POST filter that massages response headers before they hit wire. Unfortunately I had sneaky NPE in that filter that was not logged (another topic to talk about, but Zuul logging has room to improve) and instead was masked with ConnectionPoolTimeoutException hundreds requests later.
|
Closing due to inactivity. Please re-open if there's more to discuss |
Poor written "post" Zuul filter might cause response input stream not being closed and connection leaks in respective http-client connection pools.