Forum Discussion
Kevin_Stewart
Apr 23, 2014Employee
The already in progress error page, for the most part, is triggered when you attempt to access a non-APM URI:
- During the access policy evaluation, and
- With a URI that doesn't match the original URI - stored in the session.server.landinguri session variable.
Not sure if this will help you, but the following should ensure that a non-APM/non-original URI does not trigger the in progress error:
when HTTP_REQUEST {
if { ( [HTTP::cookie exists MRHSession] ) and not ( [ACCESS::session exists -state_allow [HTTP::cookie value MRHSession]] ) } {
if { ( [HTTP::uri] ne [ACCESS::session data get session.server.landinguri] ) and not ( [ACCESS::session data get session.server.landinguri] eq "" ) } {
HTTP::redirect [ACCESS::session data get session.server.landinguri]
}
}
}
The idea is this. If an HTTP request comes in that:
- Has the MRHSession cookie
- Has an access policy that is not completed, and
- The request URI does not match the landinguri variable
redirect back to the landinguri URI.