node.js:183 throw e; // process.nextTick error, or 'error' event on first tick ^ Error: ETIMEDOUT, Connection timed out

[harlentan]

Hi,
I get this ETIMEDOUT error.

node.js:183
throw e; // process.nextTick error, or 'error' event on first
tick
^
Error: ETIMEDOUT, Connection timed out
at Socket._onConnect (net.js:602:18)
at IOWatcher.onWritable as callback

When I try to use the get method to download files from the server.
Node.js 0.4.11.

I just can catch this by on("error", function{}); But I don't think it is the real timed out from the server. Because the Server we use is known as robust very much.
It's a bug of node.js?

[bnoordhuis]

It's a bug of node.js?

Probably not. Can you tell me what you've done so far to determine that the issue is with node and not some environmental influence (network routing, firewalls, proxies, etc.)?

[harlentan]

I look at the source code of http.js. When it timed out. I will try to retry the download. Because of the same url. the http.js will reuse the connect, so it will surely time out once again.

[bnoordhuis]

Because of the same url. the http.js will reuse the connect

No, that won't happen. The connection is closed on errors.

[harlentan]

Sorry. I am wrong. I get the ETIMEDOUT error because of something wrong in the network.