Ashish_205344
Aug 17, 2017Nimbostratus
Risk excepting "xml data does not comply with schema or wsdl document"
I have setup a XML Profile and getting some requests blocked due to "xml data does not comply with schema or wsdl document", after analysing the requests if my SOAPAction header is blank the request is blocked while if that comes as a URL it works. The W3S specification The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message. so I believe F5 should be respecting all the possible values here but in reality its not. I can add exception in violation settings but not sure of the risk occurred. Can any one please help here.