CirrocumulusI 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
CirrocumulusThanks 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.
CirrocumulusEdit: I was using the session.server.landinguri variable in the switch statement rather than [HTTP::uri]. ACCESS::respond did the trick! Thanks!
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.
CirrostratusLooks like what I need. What was your successful irule?
CirrocumulusBasically what was posted above in the reply underneath the marked solution. I changed from using HTTP::respond to ACCESS::respond.