delayBody doesn't trigger timeout or sockettimeout unlike testing against an actual http server

When I run https://github.com/request/request against an actual HTTP server that delays closing the HTTP request after sending headers, I get a timeout or socket timeout. When I run it against nock configured to perform a delayBody with the same time, I do not get a timeout or socket timeout.

Take a look at https://github.com/jeffcharles/nock-timeout-testcase for an executable example. Running it on my machine results in:

Request sent back error: Error: ESOCKETTIMEDOUT
Nock should have failed with timeout but didn't

How can I configure Nock to timeout the socket given headers being sent back but the response not having been ended?

[srkimir]

+1

i believe i tried same thing, following code will return then block should not execute: Hello from Google! while i would expect ETIMEDOUT

mocha test/force-req-timeout.test.js --timeout=10000

'use strict'

const chai = require('chai')
const expect = chai.expect
const nock = require('nock')
const rp = require('request-promise')

describe('force request timeout with nock', () => {
  it('should return ETIMEDOUT', (done) => {

    nock('http://www.google.com')
    .get('/')
    .delay(8000)
    .reply(200, 'Hello from Google!')

    rp({
      url: 'http://www.google.com',
      timeout: 5000
    })
    .then((data) => {
      console.log('then block should not execute: ', data)
      ...
    })
    .catch((err) => {
      expect(err.cause.code).to.equal('ETIMEDOUT')
      ...
    })
  })
})

http://stackoverflow.com/questions/36533807/how-to-etimedout-with-nock-and-request-library

[gr2m]

👋 @hugoduraes Pedro is not maintaining nock any longer, I’m trying my best to help out (and onboard new maintainers hint hint). I’m on vacation right now, I can look into it after April 22. If anyone would like to send a PR, happy to review it after unless someone beats me to it 😃