Default timeouts

[seanmonstar]

Not having a default timeout means that anyone who doesn't consider a maximum time length for a request can end up with a hung thread (with sync client) for quite a while. This could even not manifest during testing and development, and only happen in rare occasions in production, where the long hang without a cancel hurts a user.

Now, some people need a really long timeout, such as if doing "long polling", or on flaky wireless connections. But as long as there is an option for them to increase (disable?) the timeout, they should be fine.

So, what's a proper default? 30 seconds?

[KodrAus]

30 seconds seems like plenty of time in most cases. I think if you're possibly going to need more time than that in normal circumstances then you'll probably know about it.

FWIW .NET's http client decided on 100 seconds for their default timeout.

[AndreKR]

Ok, I find a default timeout a bit surprising, but I can understand the decision. However, there's no way to disable the timeout per request, is there? Just set it to 1 week or so? I'm uploading some files, which can easily take hours.