You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Returns request to http://test.com/user/tokeninfo failed, reason: Nock: No match for request GET http://test.com/user/tokeninfo
I have the feeling it compares all the rest of the headers with it.
By attaching .log(console.log) to the nock I get the following debug information:
And here the whole stacktrace:
{ Error
at OverriddenClientRequest. (C:\Users\rai\workspace\fsdsfsdfss\node_modules\node-fetch\index.js:133:11)
at emitOne (events.js:96:13)
at OverriddenClientRequest.emit (events.js:188:7)
at C:\Users\rai\workspace\fsdsfsdfss\node_modules\nock\lib\request_overrider.js:206:11
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
name: 'FetchError',
message: 'request to http://test.com/user/tokeninfo failed, reason: Nock: No match for request GET http://test.com/user/tokeninfo ',
type: 'system',
errno: undefined,
code: undefined }
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We try to do our best, but nock is maintained by volunteers and there is only so much we can do at a time. Thank you for your contributions.
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!
lockbot
locked as resolved and limited conversation to collaborators
Oct 8, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using:
nock 9.0.2,
NodeJS v7.0.0
Windows 7
By using the following code:
and then making the call with
Returns request to http://test.com/user/tokeninfo failed, reason: Nock: No match for request GET http://test.com/user/tokeninfo
I have the feeling it compares all the rest of the headers with it.
By attaching .log(console.log) to the nock I get the following debug information:
matching http://test.com:80 to GET http://test.com:80/user/tokeninfo: true
bodies don't match:
{ reqheaders: { authorization: 'Bearer VALID_JWT' } }
And here the whole stacktrace:
{ Error
at OverriddenClientRequest. (C:\Users\rai\workspace\fsdsfsdfss\node_modules\node-fetch\index.js:133:11)
at emitOne (events.js:96:13)
at OverriddenClientRequest.emit (events.js:188:7)
at C:\Users\rai\workspace\fsdsfsdfss\node_modules\nock\lib\request_overrider.js:206:11
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
name: 'FetchError',
message: 'request to http://test.com/user/tokeninfo failed, reason: Nock: No match for request GET http://test.com/user/tokeninfo ',
type: 'system',
errno: undefined,
code: undefined }
The text was updated successfully, but these errors were encountered: