Uses ECONNABORTED for timeouts instead of ETIMEDOUT

[jwbay]

Summary

Axios seems to set a code of ECONNABORTED when a request times out:

axios/lib/adapters/xhr.js

Line 107 in 0b3db5d

reject(createError('timeout of ' + config.timeout + 'ms exceeded', config, 'ECONNABORTED',

This makes it difficult to tell when a request actually timed out vs. being aborted in a different way:

axios/lib/adapters/xhr.js

Line 89 in 0b3db5d

reject(createError('Request aborted', config, 'ECONNABORTED', request));

Should ETIMEDOUT be used instead?

Context

• axios version: 0.18.0

[gillib]

This is very important to us as well. but please add this to http adapter as well as xhr

[lundn]

Would be very nice to have!

[9-lives]

how is it going?

[Kameecoding]

{
  "message": "timeout of 1ms exceeded",
  "name": "Error",
  "stack": "Error: timeout of 1ms exceeded\n at createError (webpack-internal:///./node_modules/axios/lib/core/createError.js:16:15)\n at XMLHttpRequest.handleTimeout (webpack-internal:///./node_modules/axios/lib/adapters/xhr.js:89:14)",
  "config": {
    "url": "redacted",
    "method": "get",
    "headers": { "Accept": "application/json, text/plain, */*" },
    "transformRequest": [null],
    "transformResponse": [null],
    "timeout": 1,
  },
  "code": "ECONNABORTED"
} 

as a workaround, you should be able to check the message or stack for timeout

[leolivier]

+1

[eddyson1006]

+1

[jasonsaayman]

Closing in favour of #2710

[adamtheadmin]

The ETIMEDOUT comes from node internal API's not axios'

[dvicory]

I don't see how this is related to #2710, but I do agree this should be closed. For us, this functionality is covered with clarifyTimeoutError.

[vaibhavgupta-bst]

To get ETIMEDOUT status instead of ECONNABORTED, set transitional.clarifyTimeoutError = true in the axios request config. Below is the implementation in axios module