Which problem adresses this?

This change makes it possible to configure a default value for how long curl waits before considering it a network failure. Right now it waits 60 seconds before timing out.

In my automatic testing I want to lower this threshold to maybe 10 seconds. But a bridge instance might want to have a different default timeout value. In any case, each bridge can override this timeout value in their call to getContents.

So it's keeping the current default while adding a config option? Okay, sounds good. Can you add some documentation for this to the /docs section? Thanks

Yeah the prior value was 60 because it's using the php.ini value from default_socket_timeout which is usually 60. Atleast that's what it is in debian/ubuntu for both fpm and cli. Yeah ill add to docs for it.

LGTM!

I think that eventually we want to lower this value when we introduce retry logic. E.g. if it times out for 15s, it aborts and tries again. That's for a later concern though. Ideally it has retry logic by default, which can be turned off from the client call.