Anyone know if the Jetty logs are written anywhere in the docker /standalone wiremock 🤔 We’re seeing this occasionally

<h1>Bad Message 400</h1><pre>reason: Bad HostPort</pre>

With no record of the request in the normal wiremock logs so it’s not even reaching wiremock. We’re mocking an SDK request so just wondering if theres headers or something that’s causing Jetty to blow up 🤷

You could try adding

--print-all-network-traffic

to the startup params

Cheers Tom; let me try that 👌