Rationale for setting default connectionTimeout to 1 second in ApiClient?

Hi team,

In our project, we are frequently encountering connect timed out errors, which seem to be caused by the connection timeout setting. Currently, we are not explicitly setting merchantConfig.getUserDefinedConnectionTimeout(), so the default value of 1 second is being used.

Personally, I feel that 1 second is quite short, especially considering that network conditions can vary, and sometimes a proxy is involved. We are considering increasing this timeout to around 10 seconds to see if it helps resolve the issue.

I wanted to ask:

• Is there a specific reason why the default connection timeout is set to just 1 second?
• Are there any concerns or trade-offs we should be aware of if we increase it to 10 seconds?

Thanks in advance for your insights!

Start by locating ApiClient and the handling of merchantConfig.getUserDefinedConnectionTimeout(), then inspect how the one-second default is defined and tested. The issue is resolved when the rationale for that default and the trade-offs of increasing it are documented, or the requested default change is explicitly scoped.