When I build a sidecar dubbo mesh using dubbo 3.1.8, and the consumer uses the triple protocol to call the provider, an error message is displayed: UNIMPLEMENTED: invalid content-type: application/json. How can I solve this problem?

Comment From: HeBai97

Export dubbo service com.xxx.dubbo.service.DemoService to url tri://10.xx.xx.148:50052/com.xxx.dubbo.service.DemoService?anyhost=true&application=maven-demo-dubbo-provider&background=false&bind.ip=10.xx.xx.148&bind.port=50052&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&interface=com.xxx.dubbo.service.DemoService&logger=slf4j&metadata-service-port=20885&metadata-service-protocol=tri&metadata-type=local&methods=sayHello&pid=7&qos.accept.foreign.ip=false&qos.enable=false&register-mode=interface&release=3.1.8&revision=1.0&side=provider&timestamp=1686537033729&version=1.0.0, dubbo version: 3.1.8

Comment From: AlbumenJ

@EarthChen @guohao @icodening PTAL

Comment From: pedoc

If Dubbo reuses the Spring port, this error will occur. This problem still exists on the latest 3.3.5. Is there a solution?

Comment From: zrlw

https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-triple-servlet#how-to-enable-servlet-support-for-triple

https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/protocol/tripe-3.3/

Comment From: zrlw

UNIMPLEMENTED: invalid content-type: application/json.

The message is inaccurate, dubbo-spring-boot-3-autoconfigure dependency should be added to pom.xml might be better if the project is running on springboot3.

Comment From: zrlw

it might be the provider side's issue, adding a dubbo springboot3 dependency automatic checker to the provider project might be more convenient, https://github.com/apache/dubbo/pull/15709