Do not automatically consume responses, respect original consumer.

[satazor]

Fixes #486

After investigation, the issue is that the recorder assumes that all listeners are attached after http.request's callback is called which might not be the case. That's exactly what was happening with me because since got is using promises, the data event was only attached in the next event loop.

Test case & fix added, I haven't committed the browserify bundle. I've tried to follow the coding style, let me know if something needs to be changed.

[coveralls]

Coverage remained the same at 92.614% when pulling 8795717 on satazor:request-promise into 694c421 on node-nock:master.

[satazor]

Do not merge yet, will improve the test to actually run on node 0.10.

[coveralls]

Coverage remained the same at 92.614% when pulling 4ed346e on satazor:request-promise into 694c421 on node-nock:master.

[satazor]

Good to be merged.

[coveralls]

Coverage remained the same at 92.614% when pulling 1e8f0d3 on satazor:request-promise into 694c421 on node-nock:master.

[coveralls]

Coverage remained the same at 92.614% when pulling 477f159 on satazor:request-promise into 694c421 on node-nock:master.

[pgte]

@satazor thanks!

Landed on v7.5.0

[satazor]

<3

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you!