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

ryan_75748's avatar
ryan_75748
Icon for Nimbostratus rankNimbostratus
Dec 01, 2008

monitoring WCF service with F5

we are building a client/service application inwhich the client is consuming windows communication foundation services. We presently monitor/LB other websites with F5 so we'd like to leverage that inv...
microsoft
partner
Will_F_98397's avatar
Will_F_98397
Icon for Nimbostratus rankNimbostratus
May 04, 2009
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.