Hi According to the documentation of this method -...
# libpact_ffi-users
p
Hi According to the documentation of this method -> https://docs.rs/pact_ffi/latest/pact_ffi/verifier/fn.pactffi_verifier_add_provider_transport.html, if i set the protocol to “message”, it will pick up only the message pacts right? Or will the verification also pick up http pacts as well for that provider ?
r
That is not a filter, it will try verify all pacts that are provided via a source. Depending on what interactions are found, it will use the configured transports to determine how to verify them.
👀 1
So it it gets both HTTP and message interactions, it will try verify both types.
p
oh, and so there isn’t any functionality to specify to the source and eventually to the verifier that “run verification for http pacts only” ?
r
No, but there is filtering for consumer or provider name, description, or provider states. If the message interaction has a distinct description or provider state, you can filter on that.
p
ok got it, thanks for the quick replies @rholshausen!! Also i had one more question, what is the protocol here then (message vs http). If i set the `protocol=message`and keep the
scheme=http
, what is the meaning of these two terms when i am verifying a message pact
r
Message interactions still use HTTP, but that allows you to specify a different port. With some of the language implementations, HTTP interactions go to the providers port, and message interactions go to a proxy on a different port.
I think Pact-JS does that.
p
thanks a lot, i think this clears a lot of things for me