HTTPCORE-769- Add Configurable Behavior for Handling 408 Responses in DefaultConnectionReuseStrategy #488
Conversation
This file contains 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
…n DefaultConnectionReuseStrategy. This change addresses scenarios where a server sends a 408 response without the "Connection: close" header, allowing clients to choose whether to close the connection as per RFC recommendations.
arturobernalg
force-pushed
the
HTTPCLIENT-1482
branch
from
1a2123f
to
dc8cb84
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces a change to the ´DefaultConnectionReuseStrategy´ class, allowing for more flexible handling of HTTP 408 (Request Timeout) responses. A new boolean parameter, ´forceCloseOn408´, has been added to make the connection reuse behavior configurable.