Update HTTP client config doc #20690
Merged
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
losipiuk
reviewed
Feb 14, 2024
mosabua
changed the title
mosabua
changed the title
mosabua
changed the title
Jessie212
approved these changes
Feb 15, 2024
losipiuk
approved these changes
Feb 15, 2024
- Add exchange prefix - Add max content length property
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.
Description
This came up to be added in some discussion around
exchange.http-client.max-content-lengthso I think it makes sense to add it to the list.
However ... I am not sure if we want to add this property specifically as well. In the prior PR with @Jessie212 I think we decided NOT to add that property, but it seems to be used in the field.
Additional context and related issues
#12247
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.