Forum Discussion
ASM Wildcard parameter no match except *
Hello,
I'm having some trouble creating a manual wildcard parameter that will actually be used by ASM instead of the more general * parameter.
HTTP request POST contains the following:
{"file_ids":[],"message":"Some user input","channel_id":"blahblah".....}
ASM violations are triggering on the "message" field in the above string. I'd like to create a parameter for the "message" field so I can address it directly. However, ASM uses the * wildcard parameter regardless of my attempts to create a wildcard parameter for it such as using following:
message":"(.*)","channel_id
message\":\"(.*)\",\"channel_id
"message":"*","channel_id
Any help would be appreciated.
4 Replies
Hi,
It looks like it's JSON content. Did you apply a JSON profile to your security policy ?
Bye
Yann
- sudonix_88648
Nimbostratus
Followed the article below and created the JSON profile and associated it with the wildcard parameters but no change in the behavior.
- Yann_Desmarest_
Nacreous
Hi,
It looks like it's JSON content. Did you apply a JSON profile to your security policy ?
Bye
Yann
- sudonix_88648
Nimbostratus
Followed the article below and created the JSON profile and associated it with the wildcard parameters but no change in the behavior.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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