fix: set request timeout to 4s by default #229
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 of changes:
Viewer request lambda edge timeout max is 5s which leads to unhandled exceptions when https requests take longer. Setting a default timeout for https request to 4s is a first step in avoiding requests timeout leading to unhandled errors such as:
Next step would be to anticipate lambda timeout with
getRemainingTimeInMillis()
context method and set the request timeout to this number minus a few milliseconds.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.