Describe the bug
Even if setting Content-Type in the @Headers annotation, if the payload conforms to GeneratedMessage, it will be automatically set to application/x-protobuf.
Expected behavior
It should not be automatically set to application/x-protobuf.
Additional context
We are using Connect for our server. This framework provides REST and RPC, and when making REST requests with Protobuf, it requires setting the Content-Type to application/proto. Retrofit will automatically set it to application/x-protobuf if the payload inherits to GeneratedMessage. Is there a way to not set this value automatically or to change it to application/proto?
The specification of Content-Type of Connect is here.
Describe the bug Even if setting
Content-Type
in the@Headers
annotation, if the payload conforms toGeneratedMessage
, it will be automatically set toapplication/x-protobuf
.To Reproduce Generates
Protobuf
request.Expected behavior It should not be automatically set to
application/x-protobuf
.Additional context We are using Connect for our server. This framework provides REST and RPC, and when making REST requests with
Protobuf
, it requires setting theContent-Type
toapplication/proto
.Retrofit
will automatically set it toapplication/x-protobuf
if the payload inherits toGeneratedMessage
. Is there a way to not set this value automatically or to change it toapplication/proto
?The specification of
Content-Type
ofConnect
is here.Thanks.