-
Notifications
You must be signed in to change notification settings - Fork 533
[#7589] fix (clients): check null before adding request headers in HTTPClient #7601
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
[#7589] fix (clients): check null before adding request headers in HTTPClient #7601
Conversation
It looks like the test case you added is failing. Is the test correct? |
Hi @justinmclean, This was due to mock server path collision between testGetSuccess() and testNullHeadersDoNotCauseNPE(). I've changed test data from "test" to "hank" to ensure consistency across all test methods that share the same mock server path (GET_success) |
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 for fixing this
… in HTTPClient (apache#7601) ### What changes were proposed in this pull request? Added a null check for empty headers before adding request headers in HTTPClient. Closes: [apache#7589](apache#7589) ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Added a unit test.
… in HTTPClient (apache#7601) ### What changes were proposed in this pull request? Added a null check for empty headers before adding request headers in HTTPClient. Closes: [apache#7589](apache#7589) ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Added a unit test.
What changes were proposed in this pull request?
Added a null check for empty headers before adding request headers in HTTPClient.
Closes: #7589
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added a unit test.