APM Citrix tidy session termination

Michael thank you for your response. As mentioned my main issue is that I do not think using the Storefront \ Web Interface logoff as the trigger that kills the F5 access session will work in our case as our policy on Storefront \ Web Interface idle timeout is only 20 minutes (also im sure that with our implementation when I click on "logout" on Storefront the URI does not change :-) ). Sorry if I waffled on a bit in my OP!

Sorry, your second posts confuses me even more. :( How is the idle timeout related to the forceful session termination such as initiating a Logoff from the StoreFront interface? As to the second part of your message, Citrix is using iFrames in the StoreFront implementation, so you will not see the explicit call to that URI that I mentioned in my post - but it most certainly is being made - you can observe it using your favorite tool such as Fiddler/HTTPWatch/HTTPFox, etc.

Michael thanks again. Admittedly I did not dig too deep regarding the Storefront logoff. I have used Chrome Developer Tools and can see what you are talking about. Apologies. Also after the upgrade to Storefront from Web Interface I forgot to re-enable the iRule in question so in fact (after re-enabling it and testing more) my issue is the same with both Web Interface and Storefront. I have tested it again today so here is my issue again (I will try not to waffle this time I hope!): - The iapp deploys an irule that searches for "loggedout" in a URI and uses this to kill access sessions (irule below so we know we are talking about the same thing) - Our deployment of both web interface and strorefront has a 20 minute timeout so, as expected the URI is passed that contains "loggedout" (web interface) of "Logoff" (Storefront) after 20 minutes (I modified the irule for Storefront like you said) - When this happens my access session is killed and my Citrix remote desktop is obviously killed too. My testing today has proved that this is not just idle sessions but sessions that I am very much using! (apologies I previously intimated that it was just idle sessions that this happened too - that was obviously inaccurate of me - the irule logic is obviously not monitoring the idle state) - I need to work out another solution as this irule is obviously great for monitoring for when a user purposefully clicks logoff from Web Interface \ Storefront but is no good for the above reason. And I personally cannot work out how it is any good for anyone but maybe it is my set-up somewhere else that is at fault? the irule in question (URI modified for Storefront): when ACCESS_ACL_ALLOWED { if {[HTTP::uri] contains "Logoff" } { after 2000 { ACCESS::session remove} } }