V16 CMS: Removal of MaxQueryStringLength
#7304
Merged
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 pull request updates the documentation for runtime and maximum upload size settings in Umbraco CMS to clarify the behavior and configuration of
MaxRequestLengthand related settings, especially when hosting with Kestrel. It removes references toMaxQueryStringLengthfrom Kestrel configuration examples and adds guidance on where to find current configuration values in the Backoffice UI.Documentation improvements for runtime and upload size settings:
MaxRequestLengthonly affects setups hosted with Kestrel, and added a link to themaximumuploadsizesettings.mdarticle for more information inruntimesettings.md.MaxQueryStringLengthfrom Kestrel configuration examples and related documentation in bothmaximumuploadsizesettings.mdandruntimesettings.md.📎 Related Issues (if applicable)
Fixes AB#52338
✅ Contributor Checklist
I've followed the Umbraco Documentation Style Guide and can confirm that:
Product & Version (if relevant)
V16
Deadline (if relevant)
ASAP
📚 Helpful Resources