For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Dinesh_22825's avatar
Dinesh_22825
Icon for Nimbostratus rankNimbostratus
Oct 29, 2014

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

When Client access the application through F5 he gets error " The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8)". But when he accesses the servers directly he doesn't get error.Not Sure why. Any Ideas ?

 

The VIP is pass through and SSL is offloaded at server. I tried both tcp and fastl4 profile still see the same error.

 

application delivery
design
LTM

2 Replies

  • Arnaud_Lemaire's avatar
    Arnaud_Lemaire
    Icon for Employee rankEmployee
    Oct 29, 2014

    Hi Dinesh, that is a server side issue, if don't implement http profile, there is no way we modify the content type back from the server to the end user. So there must be a publishing parameter at the application level which differentiate direct connection from connection via bigip. Do you use the same fqdn in both test ?

     

  • Dinesh_22825's avatar
    Dinesh_22825
    Icon for Nimbostratus rankNimbostratus
    Oct 29, 2014

    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 ?