Context

I'm testing a timeout scenario where the connection is delayed using .delay({head: [ARBITRARY TIME]}) and I do NOT need a reply or response sent, however in the playback_interceptor.js no matter what, a response is set to send on a timeout with the given delayConnectionInMs. When I run this timeout test on its own using JEST, an error is thrown from the respond() that runs on a timer set at the given delayConnectionInMs because my 'timeout' handler has successfully destroyed the socket/connection that the respond() function is trying to write to

Alternatives

I had to edit playback_interceptor.js and interceptor.js

Has the feature been requested before?

I do not believe so.

If the feature request is accepted, would you be willing to submit a PR?

Yes, I have the lines of code that work for me in the playback_interceptor.js and interceptor.js