[JENKINS-76231] Fix NullPointerException when Content-Type header is missing #219
+14
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a null check in ResponseContentSupplier.readCharset() to handle responses without a Content-Type header. Previously, the code would throw a NullPointerException when processing 204 No Content responses (such as those from GitHub Actions API) because it attempted to call .getValue() on a null header. The fix now checks if the Content-Type header exists before accessing its value, allowing these responses to be processed successfully.
Also added a test case to verify that responses without Content-Type headers are handled correctly.
Testing done
Ran the tests without the fix and the test failed.
Issue link
https://issues.jenkins.io/browse/JENKINS-76231
Submitter checklist