docs: Clarify max-body-size applies to requests and responses (v1.16.3) #4935
+1
−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.
Summary
This PR clarifies the documentation for the
dapr.io/max-body-sizeannotation to explicitly state that it applies to both request and response bodies, not just incoming requests.Target: v1.16 documentation (for Dapr v1.16.3 release)
Changes
Updated the
max-body-sizeannotation description in the arguments and annotations reference to clarify that it applies to:Previous Description
New Description
Why This Change?
Users were confused about the scope of the
max-body-sizeannotation. The fix in PR dapr/dapr#9151 (targeting v1.16.3) ensures binding components also respect this annotation, fixing issue dapr/dapr#9177.This documentation update helps users understand:
Related Issues/PRs
Checklist