Forum Discussion
Dick_Piccard_72
Nimbostratus
May 22, 2009iRule for screening form submission to script
Our security team believes that a particular application is so sensitive that we should let the submitted data reach the server only if it passes content-based screening. The idea would be to confirm that the fields and values submitted matched those that are valid (the form will not have any free-response -- text or textarea -- fields, only radio buttons, check-boxes, and selects). Valid input would be passed along intact to the intended server for the script to process; we haven't decided yet whether invalid input should result in immediate failure, or in pooling to a different pool, where the server would respond with an error page, on the off-chance that a human was at the other end.
This form is coded for method="POST" -- but knowing how to deal with method="GET" might also be useful, later.
Looking at the CodeShare iRule samples, I noticed "HTTP Payload Collection"; is this a sensible starting point? Is there a better starting point? Are there any particular pitfalls to be alert to as we start down this way?
Thanks in advance for all advice.
1 Reply
- dennypayne
Employee
This kind of thing is precisely what the ASM module is for (Click here).
That said, yes you could use HTTP::collect, parse the payload for various different conditions (probably using regex), and accept or reject (or send to an error pool) the connections based upon what you find.
Denny
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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
