Forum Discussion
Logan_Ramirez_5
Nimbostratus
Nimbostratussoap monitor failing
i have a soap monitor setup on v9.3.1build58.0
monitor web_monitor_soap {
defaults from soap
method "IsServerWorking"
namespace "http://tempuri.org/"
param type "bool"
protocol "http"
return type "bool"
return value "true"
urlpath "/verifyserverstate/serverfunctions.asmx"
}
and am pointing it to a pool member on :80, but the member is flagged down.
From capturing the frames, it appears the SOAPACTION information is missing from the header:
POST /verifyserverstate/serverfunctions.asmx HTTP/1.1
Host: 192.168.1.46
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction:
Where it should look like:
POST /verifyserverstate/serverfunctions.asmx HTTP/1.1
Host: 192.168.1.46
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://tempuri.org/IsServerWorking"
Any thoughts on why that SOAPAction value is missing in the request from the f5?
dce3435_21095I also have the same problem, the soapaction is missing, our F5 is using easysoap 0.6 and it is trying to talk to a .net web service using soap 1.1
I have successfully built an easysoap 0.6++ client (which the F5 also uses) and ran it successfully against our server. But the F5 ALWAYS leaves out the SOAPAction.
Marius_FrankowsHi,
I do have the same problem within my SOAP monitor right now. Did you already solve this problem or find out how to figure out how to fix it ?
thanks,
Marius
hoolioCirrostratus
I'd suggest opening a case with F5 Support on this to find out more.
Aaron- There is currently a known issue CR78000 that the SOAP action parameter is not supported in the 9.x software.
- hoolioThanks for the info. It seems quite strange that bigd would strip one specific header from the request send string. Did F5 Support give any background on the issue?
Thanks,
Aaron
