Fix for #947

[martinkuba]

The failing test was checking that a call to www.amazon.com was returning data. This URL does not return any data any longer - changed it to one that does.

[coveralls]

Coverage increased (+0.6%) to 92.654% when pulling a2f170f on martinkuba:master into 35c76e3 on node-nock:master.

[0xcaff]

lgtm

[drone@drone tmp]$ curl --verbose www.amazon.com
* Rebuilt URL to: www.amazon.com/
*   Trying 104.95.239.148...
* TCP_NODELAY set
* Connected to www.amazon.com (104.95.239.148) port 80 (#0)
> GET / HTTP/1.1
> Host: www.amazon.com
> User-Agent: curl/7.54.1
> Accept: */*
> 
< HTTP/1.1 302 Moved Temporarily
< Server: AkamaiGHost
< Content-Length: 0
< Location: https://www.amazon.com/
< Date: Fri, 14 Jul 2017 00:29:17 GMT
< Connection: keep-alive
< 
* Connection #0 to host www.amazon.com left intact

[ianwsperber]

Awesome @martinkuba! Thanks for stepping up again to help.

[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!