RestClient idleTimeout being hard-limited to 30 seconds

Hi all,

The current RestClient logic caps idleTimeout at 30 seconds even when timeoutSeconds is configured to a higher value, which can cause long-running REST calls to time out earlier than expected.

I’ve opened an issue describing the problem and a PR that removes the hard-coded limit and restores the original intent of honoring the configured timeout while keeping the existing safety buffer.
View Issue on Github
View PR on Github

Would appreciate a review and any feedback.

Although HTTP requests shouldn’t take so long, it makes sense to open the limit to whatever people choose. +1