Forum Discussion
"ACCESS::disable" - doesn't work when try to bypass Access Policy with an iRule below:
are you sure the path matches the string you use? easy way is to add an log local0. "string to hit" to check it matches what you think.
also the other question you mention adds some things to be case insentive: switch -glob [string tolower [HTTP::path]]
Thanks! Yes, i am 100% sure the path match/correct, and it shows in the logs. try "switch -glob [string tolower [HTTP::path]] " does not work either. But if we switch the "ACCESS::enable" to "ACCESS::disable" and "ACCESS::disable" to "ACCESS::enable" . the funcationality work as expected, the path really "enable" .... but that is not what we want. so i think there is bug with "ACCESS::disable". thank!!
- randylee168Aug 19, 2024Nimbostratus
not sure why this "Mark as Solution" since it does not work, again, the "ACCESS::enable" work very well, but "ACCESS::disable" does not work if it is not in "default" , any suggestion? thanks
- randylee168Aug 19, 2024Nimbostratus
Hello, can we please have update? thanks
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