Forum Discussion
IoF
May 12, 2022Altostratus
ASM/WAF policy - Parameter value type was determined to be "XML value" but really it is "HTML"
Hi, hoping someone can help with this issue. F5 WAF suggested that the parameter "text" should be "XML value". I agreed and and I'm using the default XML content profile. However the actual value l...
Pache
Aug 04, 2023Nimbostratus
You could define /aa/bb on the allow URLs and add to it a Header Based Content Profile:
Request Header name: Content-Type
Request Header Value:* application/x-www-form-urlencoded *
Request Body Handling: Form Data
Profile Name: N/A
Then you can create a parameter text and select the parameter value type to XML value. Then use the XML default content profile
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects