Forum Discussion
iRule Not Firing after APM policy completes
- May 12, 2022
I have not tested it but you might check out the ACCESS::respond command. https://clouddocs.f5.com/api/irules/ACCESS__respond.html
I have not tested it but you might check out the ACCESS::respond command. https://clouddocs.f5.com/api/irules/ACCESS__respond.html
- JustCooLpOOLeMay 13, 2022Cirrocumulus
Thanks JoshBecigneul ! That works for a single default page but if I add another line to the switch such as:
when ACCESS_ACL_ALLOWED { set uri "myuri" switch -glob $uri { "myreport.hmtl" { ACCESS::repond 200 content {ifile get "reportMainPage"] } "myotherreport.html" { ACCESS::respond 200 content {ifile get "newPage"] } } }
These work fine individually but within the reportMainPage ifile, there is a link to move to the "newPage" ifile. When I click on it, the main page continues to exist even though the URL is updated.
- JustCooLpOOLeMay 13, 2022Cirrocumulus
Edit: I was using the session.server.landinguri variable in the switch statement rather than [HTTP::uri]. ACCESS::respond did the trick! Thanks!
- May 14, 2022
Sounds good. session.server.landinguri only gets set one time during access policy execution, which can be good to override if you want to force the user to connect to a specific URL.
- The-messengerJul 28, 2023Cirrostratus
Looks like what I need. What was your successful irule?
- JustCooLpOOLeJul 28, 2023Cirrocumulus
Basically what was posted above in the reply underneath the marked solution. I changed from using HTTP::respond to ACCESS::respond.
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