monitoring WCF service with F5

We have the same issue with WCF/SOAP. Turns out the SOAPAction header was not being posted in the packet headers. The developers managed to code the health monitor in there application to trap the message the client (F5) was sending and return a different message (e.g. true/false string indicating the status of the application).

 

 

From what I've been told this is a bug with BigIP (not EasySOAP as it may appear) but is not going to be fixed anytime soon.

 

 

Tested with 9.3.x and 9.4.x streams. Have not tried this with BigIP 10.0 yet.