Matt R. Wilson

Could you link to a public repo instead of a zip file please.

Implementation-wise this feature revolves less around `nockBack` and more around how the core Scopes manage ports. Currently, when an non-regex is passed to a `Scope`, it will parse the URL...

Is it currently possible to use `filteringScope` via Nock Back though?

The most recent example of the current behavior causing confusion https://github.com/nock/nock/discussions/2322 fyi @ebisbe

I didn't dig into this, but I was curios if this was still an issue. I can confirm on Node 14.2, Nock 13.0, and Axios 0.19.2, this is still not...

We need a failing test that's client agnostic.

Off-hand, I think you access the req directly using `this` in the `post` callback. The base issue IMO is one we've discussed a lot in the past in that there...

@lloan thank you very much for providing the repo. It made figuring out the issue very straightforward. There is a fundamental issue with how you're attempting to test, at least...

I don't know. A lot of nock comes from years of if-y documented incremental changes. My comment is not a statement that it _should_ behave like it does, just that...

Thanks for the request @pke Some things to come to mind right off the bat: - The current implementation of `getPeerCertificate` on Nock's mock `Socket` class is just flat out...