Extend default timeout on certain path patterns #53
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
We ran into a use case where certain longer running endpoints needed their timeout to be extended beyond what the rest of the API required due to longer running legacy processes that couldn't be changed for backwards compatibility. There was a limitation in this middleware package that we couldn't easily extend certain paths from the normal timeout.
Extending certain paths, path patterns or lists of paths allows us to configure endpoints in a more controlled way, instead of updating the whole app to allow longer running timeouts.
Changes
timeout
will be used.Example Usage