Hi running beta58 and trying to debug a consumer contract test where the URL path is matching when it shouldn't be

[2022-07-27T08:00:39Z INFO  pact_mock_server::hyper_server] Received request HTTP Request ( method: GET, path: /foo/1/bar, query: None, headers: Some({"accept": ["application/json"], "authorization": ["Bearer undefined"], "user-agent": ["node-fetch/1.0 (+<https://github.com/bitinn/node-fetch>)"], "accept-encoding": ["gzip", "deflate"], "connection": ["close"], "host": ["127.0.0.1:52198"]}), body: Empty )

[2022-07-27T08:00:39Z INFO  pact_matching] comparing to expected HTTP Request ( method: GET, path: /fooBlah/1/bar, query: None, headers: Some({"Accept": ["application/json"]}), body: Missing )
[2022-07-27T08:00:39Z INFO  pact_mock_server::hyper_server] Request matched, sending response HTTP Response ( status: 200, headers: Some({"Content-Type": ["application/json"]}), body: Present(266 bytes, application/json) )

I'm looking for strings like

comparing to expected HTTP Request

in the pact and pact-core codebase but not having any luck - could someone point me at where these are? [Some GLIBC-related blockers prevent me moving to beta62 at this time]

Just dropped off for the day, but the core matching is all in here: https://github.com/pact-foundation/pact-reference/tree/master/rust

Thanks @Matt (pactflow.io / pact-js / pact-go)!

Interesting. My assumption is that the path should match exactly (on the consumer side), as I didn’t think it was a matcher