Thanks Aaron. Very good info. I was heading down those lines, but how do I get the iRule to capture the button click on my html page delivered to the user?
Here is a snippet of what I have for the html on my tos.html page.
I Agree
This just seems to bring me back to the tos.html page.
Also, the only way that I can see (with my limited knowledge of the Big IP traffic flow sequence and when the events are called) to do it is to have the iRule set a variable or cookie in the same conditional statement as the HTTP::respond. By doing this, though, the user won't actually have to click the 'I Agree' button to have the cookie or variable be set, instead, all they would have to do is visit the page. I would much rather know that they clicked the 'I Agree' button.
Here is some of the iRule:
when CLIENT_ACCEPTED {
set consent_monitor "NotAgree"
log local0. "CLIENT_ACCEPTED"
}
when HTTP_REQUEST {
if { $consent_monitor == "NotAgree" } {
log local0. "Client has not agreed to monitoring. Sending consent page..."
set origUrl "[HTTP::host][HTTP::uri]"
log local0. "original URL = $origUrl"
HTTP::respond 200 content [subst $::html_data]
set consent_monitor "Agree"
}
}
Any thoughts?...clear as mudd?
Reiss