CXF-9192: Inconsistent best effort read of body by web-client when protocol is HTTP/2#2792
Merged
reta merged 1 commit intoapache:mainfrom Dec 27, 2025
Merged
CXF-9192: Inconsistent best effort read of body by web-client when protocol is HTTP/2#2792reta merged 1 commit intoapache:mainfrom
reta merged 1 commit intoapache:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The
InputStream::available()was/is always known to be "best effort" and it is in case ofjdk.internal.net.http.ResponseSubscribers.HttpResponseInputStream. CXF has no knowledge if the response will come any time soon or is empty (so we could not really wait / block here).Considering the options, probably the only way we could make sure the response stream is really empty is to try to issue
InputStream::readwhich may block.