feat: Allow MAX_URI_LEN configuration via environment variable #3959
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.
Add ability to configure maximum URI length through HYPER_MAX_URI_LEN environment variable while maintaining the default value when the variable is not set.
Motivation
We have some legacy applications which supports pretty big URI. We are adding a new component built in rust (using hyper) which will handle this communication in future. Requests get rejected with if they are above 64K hardcoded limit in the hyper crate. So making it configurable via ENV variable.
#3960