Skip to main content
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Source Link

curl has a "connect timeout" option:

--connect-timeout <seconds>

If your "tool" is a script, you could manually edit that into there. But http://unix.stackexchange.com/a/148926/77959https://unix.stackexchange.com/a/148926/77959 is even better - edit the curl-config!

curl has a "connect timeout" option:

--connect-timeout <seconds>

If your "tool" is a script, you could manually edit that into there. But http://unix.stackexchange.com/a/148926/77959 is even better - edit the curl-config!

curl has a "connect timeout" option:

--connect-timeout <seconds>

If your "tool" is a script, you could manually edit that into there. But https://unix.stackexchange.com/a/148926/77959 is even better - edit the curl-config!

deleted 49 characters in body
Source Link
Jeff Schaller
  • 68.8k
  • 35
  • 122
  • 267

curl has a "connect timeout" option:

--connect-timeout <seconds>

If your "tool" is a script, you could manually edit that into there. But http://unix.stackexchange.com/a/148926/77959 is even better - edit the curl-config! I'd vote that up, once I have enough reputation.

curl has a "connect timeout" option:

--connect-timeout <seconds>

If your "tool" is a script, you could manually edit that into there. But http://unix.stackexchange.com/a/148926/77959 is even better - edit the curl-config! I'd vote that up, once I have enough reputation.

curl has a "connect timeout" option:

--connect-timeout <seconds>

If your "tool" is a script, you could manually edit that into there. But http://unix.stackexchange.com/a/148926/77959 is even better - edit the curl-config!

Source Link
flowtron
  • 356
  • 2
  • 6

curl has a "connect timeout" option:

--connect-timeout <seconds>

If your "tool" is a script, you could manually edit that into there. But http://unix.stackexchange.com/a/148926/77959 is even better - edit the curl-config! I'd vote that up, once I have enough reputation.