Use TCP_KEEPALIVE only if TCP_KEEPIDLE is not defined #8539
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The change based on a comment for TCP_KEEPALIVE.
I try using a CURLOPT_TCP_KEEPALIVE option. For TCP connections my application use lwIP library. The library defines both TCP_KEEPALIVE and TCP_KEEPIDLE. Both are responsible for the same thing, but TCP_KEEPALIVE is in milliseconds and TCP_KEEPIDLE is in seconds. After set TCP_KEEPIDLE correctly, TCP_KEEPALIVE overwrites changes. In the end, the application does not work as intended.