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
I am able to work around this and keep allowUnmocked=true by using a filteringPath to remove the query. Is this a bug or am I missing something here? Thanks!
The text was updated successfully, but these errors were encountered:
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
Sep 13, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With the code above, my request does NOT match and goes to google.com.
$ node nockTest.js
response.statusCode: 404
By changing allowUnmocked to false, I get:
$ node nockTest.js
matching https://www.google.com:443?user=fred to GET https://www.google.com:443/abc with query({"user":"fred"}): true
Match!
I am able to work around this and keep allowUnmocked=true by using a filteringPath to remove the query. Is this a bug or am I missing something here? Thanks!
The text was updated successfully, but these errors were encountered: