http.timeout in milliseconds or allow float

[sergejostir]

Hello.

Is there a specific reason why http.timeout config option only accepts integers which are considered seconds? My proposal is to either accept integer and interpret it as milliseconds or allow setting this config value to a float (so we can set for example 3.5 seconds).

[drakkan]

Hi,

thank you for your suggestion. To avoid a backward incompatible change maybe we could accept float values. Does 3.5 seconds make a big difference to your use case compared to 3 or 4?

[sergejostir]

Well not really. I wanted to set timeout 250ms higher than my gateway, so the sftpgo's client won't timeout before the gateway does, but it will also do just fine with 1 second higher.

[drakkan]

It is supported now 8ecf64f please confirm that it works as expected, thank you