-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
HttpSink. Fix bad response handling. #139
Conversation
After a bad response, connection.getInputStream () returns null. I'm adding a check for this. If the answer is bad - try to close ErrorStream.
HttpSink. Fix bad response handling.
@filippovmn : thank you for the pull request! Is there an easy way to reproduce the faulty behavior in order to validate the patch? |
@bessbd |
Checks the possibility of selectively skipping erroneous events
@bessbd |
Validation of the use of сonfiguration for critical responses
I've run the tests and it looks fine to me. |
LGTM, +1 |
@filippovmn : thank you for the patch! |
After a bad response, connection.getInputStream() returns null. This patch adds a check for this. This closes apache#139 Reviewers: Bessenyei Balázs Donát (filippovmn via Bessenyei Balázs Donát)
After a bad response, connection.getInputStream () returns null. I'm adding a check for this. If the answer is bad - try to close ErrorStream.