Request Header with Content-Encoding:UTF-8 failed in between Message Router and Processor - Error Unsupported Content Type

[adithyaseelam]

@Dino-at-Google

We are experiencing issues on APIGEE when request header has Content-Encoding:UTF-8.

We can see the error message in JSON format saying that Unsupported content type.

But the request cannot be seen in trace, I guess its been blocked between message router and message processor.

Could someone please help us.

Let me know if you need any info.

Thanks

Adithya