Timeout value for https:// is capped at 5000ms, event it was set higher
Opened this issue · 2 comments
ggsubs commented
It appears timeout values for https:// are maxed out at 5000ms. Higher values are accepted but not acted on. All timeouts capped at 5 seconds.
mklatsky commented
We are noticing the same behavior. We are needing longer timeouts to work with some of our backend systems which have longer timeouts.
rickymoorhouse commented
This is because there is a timeout set in the config as well for 5 seconds.
See monitor > timeout in https://github.com/fzaninotto/uptime/blob/master/config/default.yaml#L14
I've successfully increased this to have a longer timeout for some checks