Hi, has anyone had an issue when using a Wiremock...
# help
ž
Hi, has anyone had an issue when using a Wiremock as a proxy, the request’ header, user-agent is rewritten and passed to the server as
apache-httpClient/5.3.1 (Java/17.0.9)
instead of the custom header that was set by the client (in my case an Android device)? I would like to know how I can avoid this scenario, because if I’m not forwarding the right user-agent, my client gets blocked by the server and returns code 403.