error on timeout - 200 and an error after timing out what gives?

[dugaquilin]

Hi,

I'm new to node.js and even more to this module. Big fan, like the work you have done.

I'm doing an HTTP GET and it returns a 200 after a redirect, which is fine, but then it also returns an error after timing out.

The web site is working, I don't understand why I'm getting an error.
I was thinking of extending fetch, but it seems I can't export fetch as it is not a function.

Any insights?

[jimmywarting]

do you have any sample code that you can show us what you are doing?

[jimmywarting]

Hmm, without actually testing your code it looks to me that you aren't dealing with the response
it's always best to consume the response or abort the hole request if you no longer need it

so eg:

const getData = async url => {
  const response = await fetch(url);
  await response.arrayBuffer() // consumes the body and dose nothing with it
}

or:

const getData = async url => {
  const ctrl = new AbortController()
  const response = await fetch(url, { signal: ctrl.signal })
  ctrl.abort()
}

It could also be recommended to try out using http method HEAD, this will tell the server to just perform a get request but you aren't actually intrested in the body, only the response headers

[dugaquilin]

Oh, i never knew about the HEAD vs GET. Thanks.

[dugaquilin]

What I don't understand is, I'm doing the catch(error) and it seems to be terminating the calling loop. Since my loop is iterating over URLs I'd like to continue with the loop even though that one specific URL is broken.

Thank you for your code example. It is advanced to me, it will take me a while to understand it.... Again.. I'm old school programmer new to node.js.

[dugaquilin]

I found that the page i am probing is actually not responding.
anyways... I am looking to capture the issue, and continue on. that is gracefully register the issue and continue on, but it is stopping.

I am probing multiple web sites and want to capture and continue but it is stuck.

FetchError: request to https://mysite.com/ failed, reason: connect ETIMEDOUT {ip address}

I'd like to tread the ETIMOUT as a trappable error code vs a crash. For example, capture the ETIMEOUT (because the site is non-responsive) then assign a status to it, then move on to the next url.

[dugaquilin]

My specific scenario is this.

1. the DNS entry returns an IP, so the site is "registered"
2. the FQDN is non-responsive - probably because the site is turned off and is non-responsive, so either the site was depricated, or the site is down, in which case I want to flag it as an issue and move on to probing the next site. to me the lack of response is not the end of the world, it is just one of the expected outcomes