The content type does not match the content type of the binding

Thanks for the reply Arnaud! Fqdn for f5 VIP is different than that of server IP. Even if we use http profile, since cert is offloaded at server, we cannot decrypt the traffic and modify the content type. When client access VIP FQDN with its URI, server redirects to its own FQDN with same URI. There is no redirect configured on F5. I am guessing since the client is expected to see VIP FQDN in response but since it sees server FQDN in response that might be the reason. Any thoughts on it ?