When self-hosting a Pact Broker in, for example AWS or Azure, it is common to have some kind of web application firewall (WAF) in place. One use case for WAFs that seems to be fairly common, is to use the User-Agent HTTP header for filtering of requests (example from AWS docs).
The pact_verifier/pact_verifier_cli on master does currently not set a User-Agent which means that requests get blocked before they reach the Pact Broker.
This also affect the Pact libraries in other languages using this library.
When self-hosting a Pact Broker in, for example AWS or Azure, it is common to have some kind of web application firewall (WAF) in place. One use case for WAFs that seems to be fairly common, is to use the
User-AgentHTTP header for filtering of requests (example from AWS docs).The
pact_verifier/pact_verifier_clionmasterdoes currently not set aUser-Agentwhich means that requests get blocked before they reach the Pact Broker.This also affect the Pact libraries in other languages using this library.