How to hide TCP_KEEPINTVL and TCP_KEEPCNT errors #19520
-
|
Dear Curl community, Windows 7, Curl 8.16.0. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 11 replies
-
|
Do they go away if you add use the --no-keepalive option? You could add that to
your .curlrc file (called _curlrc on Windows I think).
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, But why it's not a default, why we have to deal with these errors by means of extra switch? I remember a time when there were no such errors in logs. And nowadays if you search for Curl connection logs, you will find thousands of links that mention such error message. But why accept this behavior if the function doesn't work as intended and produce an error anyway? |
Beta Was this translation helpful? Give feedback.
-
|
I wouldn't actually expect to see these messages unless you're using
--keepalive-time. Are you sure that option isn't being given anywhere, either
on the command-line or in a .curlrc file?
|
Beta Was this translation helpful? Give feedback.
-
|
Dan, thing is I don't have .curlrc file (to keep things as portable as possible). |
Beta Was this translation helpful? Give feedback.
-
|
curl defaults to setting keep-alive. The issue here seems to be that Windows 7 doesn't support them? I was not aware. |
Beta Was this translation helpful? Give feedback.
-
|
Daniel, I believe Windows 7 supports some TCP options, but not all of them. Should I create an issue to troubleshoot further? Related:
|
Beta Was this translation helpful? Give feedback.
-
|
It's Windows, we can't expect this to have a simple solution but we can certainly work on improving this. Currently the code does a build-time decision on what code to run, and if it is built for >= Windows 10, version 1709, then it will set options that if the executable runs on an older Windows version fail. Clearly, this function would ideally instead check the Windows version in run-time and opt to only use the keeplive options that are known to work. Alternative takes:
|
Beta Was this translation helpful? Give feedback.
-
|
TCP tracing sounds good to me. |
Beta Was this translation helpful? Give feedback.
-
|
Agree, on Windows this would ideally be a runtime check, with something like: curlx_verify_windows_version(10, 0, 16299, PLATFORM_WINNT, VERSION_GREATER_THAN_EQUAL)edit: in addition to the build-time check, because some macros need certain newer SDKs and/or built-time settings. Just to make it less of a brain-breaker! |
Beta Was this translation helpful? Give feedback.
-
|
Made #19527 where I converted those info messages to tracing. |
Beta Was this translation helpful? Give feedback.
-
|
It works as expected, although there are now a few lines that I didn't expect. $ curl --doh-url https://dns10.quad9.net/dns-query -4ksvo nul -m 5 https://nine.testrun.org/
Note: Using embedded CA bundle, for proxies (230814 bytes)
* Host nine.testrun.org:443 was resolved.
* IPv6: (none)
* IPv4: 168.119.244.218, 37.218.247.14, 116.202.233.236
* Trying 168.119.244.218:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [311 bytes data]
* SSL Trust: peer verification disabled
* Connection timed out after 5001 milliseconds
* closing connection #0Those lines |
Beta Was this translation helpful? Give feedback.
-
|
#19527 is now merged! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you and @icing for making the necessary changes to the Cur's code with all seriousness and quickly. Younger developers, having heard that I am a Windows 7 user, probably wouldn't even respond. And you have the bar of human attitude remaining at the highest level for many years. |
Beta Was this translation helpful? Give feedback.
It's Windows, we can't expect this to have a simple solution but we can certainly work on improving this.
Currently the code does a build-time decision on what code to run, and if it is built for >= Windows 10, version 1709, then it will set options that if the executable runs on an older Windows version fail.
Clearly, this function would ideally instead check the Windows version in run-time and opt to only use the keeplive options that are known to work.
Alternative takes:
tcptracing