Hi all, I’m running wiremock 3.9.1 in a container. I am mocking grpc calls from a browser, and using

envoy

to proxy calls before hitting wiremock. Unfortunately the client app is throwing “missing trailers” error as it expects the response to contain grpc trailers. Is it possible to log the request and response headers from wiremock? I am using

--verbose

argument but not getting much information from that.

Host: [localhost:8080]
User-Agent: [curl/8.5.0]
Accept: [*/*]

1. Do you have the gRPC extension (correctly) installed in WireMock? 2. What happens if you hit WireMock directly?

Yes, extension is installed correctly as I am able to hit wiremock using curl with no problems. i’m using connectrpc library on the client app in the browser, if i use the grpc transport protocol there is no issue, but if i use the grpc-web transport protocol it will throw

missing trailers

error. Since I am using

envoy

to proxy grpc-web calls to wiremock I would assume that the required response headers expected from the front end would be intact. Just a fyi, I previously used

gripmock

as grpc mock server with this setup and that was also working fine.

I don’t have any magic bullets unfortunately. I’ll need to be able to replicate this locally to have any realistic chance of figuring out what’s happening. One possible shot in the dark is that it’s related to Jetty 11 (which is the only version the gRPC extension works with at the moment). I’m going to try to get it working with 12 over the next couple of weeks so if I had a working test setup for this issue I could test this with it also.

No worries, I’ve raised an issue and included the source code and hopefully will make it easier to debug. Thanks for your time.