WireMock

Hi <@U04V868UX45> WireMock doesn’t support Protobuf right now, but you could write a custom matcher extension to do this

<@U03N1E342B0> Looks like custom matcher is for extensive use. Like if we are looking for something specific in request . However, my requirement is simple: I just look for the URI and header tag. If it matches then it need to return the response back as a protobuf

So, would I still need custom matcher for this?

If you don’t need to match on a protobuf request, and just need a protobuf response then you shouldn’t need to write an extension.

You’d need to encode the protobuf as base64 then return it as a binary response

Are you configuring your stubs via Java or JSON?

In that case you should be able to put the protobuf response in a file under the `__files` folder and create a stub mapping like:
```{
    "request": {
        "method": "POST",
        "url": "/proto"
    },
    "response": {
        "status": 200,
        "bodyFileName": "my-data.proto" // The name of the file under __files
    }
}```

<@U03N1E342B0> I tried use the suggested way, and I see exception on client side when I deserialize 'EntityResponse response = response.getEntity(EntityResponse.class)'
_com.google.protobuf.InvalidProtocolBufferException$InvalidWireTypeException: Protocol message tag had invalid wire type._
The message is encoded and sent as binary. Not sure what am I missing here