Forum Discussion
iRule to store cookie in table
The part about your proposed rule that may be challenging is all the additional info you want to store in the table. What will you do with that info? If you don't plan on using it or logging it, its really a waste of memory space. Also, remember the table command is just a hash table(key value pair) so saving all that additional info about the user won't be in the same record that you want to increment. I would suggest the storage of all the info be done with High Speed Logging off box and just use the logic of deciding if a users has the required cookie to hit the URI to block connections. That may help much more with historical research while at the same time lessening the memory and CPU load of the iRule.
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