FoleyJH_30150
Jul 11, 2012Nimbostratus
ASM flagging SOAP/XML message content as URL Parameters
I have an inbound POST to my web application that uses a SOAP/XML content format. This is the first time I have had to work with this. I used Policy Builder to generate the majority of the security policy. It has correctly identified the URL's and associated parameters. However, without policy builder enabled the POST fails with illegal parameter and flags the following as a parameter:
< div>
How do I indicate to the ASM that this is content and not parameters and values.
Thanks in advance.
/DIV>