Skip to content
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

Closed
wants to merge 6 commits into from

Conversation

filippovmn
Copy link
Contributor

After a bad response, connection.getInputStream () returns null. I'm adding a check for this. If the answer is bad - try to close ErrorStream.

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.
@bessbd
Copy link
Member

bessbd commented Jul 2, 2017

@filippovmn : thank you for the pull request!

Is there an easy way to reproduce the faulty behavior in order to validate the patch?
Do you think there is an easy way to add a unit test for this?

@filippovmn
Copy link
Contributor Author

filippovmn commented Jul 4, 2017

@bessbd
OK. I think it's not difficult

Филиппов Михаил Николаевич added 3 commits July 4, 2017 17:27
Checks the possibility of selectively skipping erroneous events
@filippovmn
Copy link
Contributor Author

@bessbd
I added a test that checks the ability to ignore some types of errors (in this case: 401) using the configuration.

Validation of the use of сonfiguration for critical responses
@bessbd
Copy link
Member

bessbd commented Jul 5, 2017

I've run the tests and it looks fine to me.
I'll leave some time for others to review and leave comments if they have any.

@bessbd
Copy link
Member

bessbd commented Jul 12, 2017

LGTM, +1
I'm about to commit this

@asfgit asfgit closed this in c570a51 Jul 12, 2017
@bessbd
Copy link
Member

bessbd commented Jul 12, 2017

@filippovmn : thank you for the patch!

szaboferee pushed a commit to szaboferee/flume that referenced this pull request Jul 31, 2017
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants