curl timeout problem

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • news

    curl timeout problem

    Hi,
    I'm having a problem with the cURL library.
    It doesn't seem to obey the 'timeout' parameters.

    I set the CURLOPT_CONNECT TIMEOUT to, say, 1 second,
    and CURLOPT_TIMEOUT to whatever value.

    Then I'm fetching (via a GET request) some page
    from a _nonexistent_ domain - and I have to wait around 4 seconds
    for the timeout error to show up. (name lookup error)

    So - what's the use of CONNECTTIMEOUT and TIMEOUT?
    Why I have to wait 4 seconds, while I set the connect timeout
    to 1 second?

    TIA, Regards
    -news
  • Rik

    #2
    Re: curl timeout problem

    news wrote:
    Hi,
    I'm having a problem with the cURL library.
    It doesn't seem to obey the 'timeout' parameters.
    >
    I set the CURLOPT_CONNECT TIMEOUT to, say, 1 second,
    and CURLOPT_TIMEOUT to whatever value.
    >
    Then I'm fetching (via a GET request) some page from a _nonexistent_
    domain - and I have to wait around 4 seconds
    for the timeout error to show up. (name lookup error)
    >
    So - what's the use of CONNECTTIMEOUT and TIMEOUT?
    Why I have to wait 4 seconds, while I set the connect timeout
    to 1 second?
    Well, maybe looking up an ip for the host might not be counted as valid
    for the timeout (which might be time to let the server respond, and we
    first have to know that server). What happens if you choose a
    non-existent ip instead of DNS?

    --
    Rik Wasmus

    Estimated date being able to walk again: 01-05-2007.
    Less then a week, hurray!

    Comment

    • news

      #3
      Re: curl timeout problem

      Hi,
      I'm having a problem with the cURL library.
      It doesn't seem to obey the 'timeout' parameters.
      >
      I set the CURLOPT_CONNECT TIMEOUT to, say, 1 second,
      and CURLOPT_TIMEOUT to whatever value.
      >
      Then I'm fetching (via a GET request) some page from a _nonexistent_
      domain - and I have to wait around 4 seconds
      for the timeout error to show up. (name lookup error)
      >
      So - what's the use of CONNECTTIMEOUT and TIMEOUT?
      Why I have to wait 4 seconds, while I set the connect timeout
      to 1 second?

      Sorry, my mistake.
      CURL timeout works fine - the problem was that I've set a fractional
      timeout - like 0.4 seconds - then the timeouts were strange.
      When I now set it to 1,2 or 3 seconds then it timeouts OK.
      Checked for domain lookups and IPs.

      So actually the question is, if it's possible to set a fractional timeout.

      Regards
      -news

      Comment

      • rahul sinha

        #4
        Re: curl timeout problem

        On Apr 26, 2:55 pm, news <a...@inetia.pl wrote:
        Hi,
        I'm having a problem with the cURL library.
        It doesn't seem to obey the 'timeout' parameters.
        Can you show me the code ..
        >
        I set the CURLOPT_CONNECT TIMEOUT to, say, 1 second,
        and CURLOPT_TIMEOUT to whatever value.
        >
        Then I'm fetching (via a GET request) some page
        from a _nonexistent_ domain - and I have to wait around 4 seconds
        for the timeout error to show up. (name lookup error)
        >
        So - what's the use of CONNECTTIMEOUT and TIMEOUT?
        Why I have to wait 4 seconds, while I set the connect timeout
        to 1 second?
        >
        TIA, Regards
        -news

        Comment

        Working...