How to make a WSS request not restart the session timeout
hi, We have a page that is used to notify the application if the user is in session or not, without interferring with the session timeout itself. This page is accessed by the client automatically every X seconds. This is the code: if {$httpPath == "/pagename"} { if {([HTTP::cookie value MRHSession] != "") && ([ACCESS::session exists -state_allow]) } { HTTP::respond 200 content Yes SomeHeader Yes } else { HTTP::respond 200 content No SomeHeader No } ACCESS::disable return } Now the application team start using some asp.net component called SignalR which uses WSS, let's say the path is /signalr. This path is also accessed automaticaly every X seconds by the client, and thus restarts the session timeout counter and the app never disconnect. I need to do the same intervention like the code above does, only with this /signalr page. Problem is that unlike with the current/pagename path, if I add the /signalr path to the IF, it blocks the request from getting to the app server and breaks the app. Anyone familiar with this component or know why it acts differently? Thanks
Application Logged Out when Idle . . .
Hey friends, I have a problem .... when we access application using a server directly, it is stabil (NOT LOGGED OUT), but when accessing it using the F5 application and idle, the application back to the login menu (LOGGED OUT), but if we click on the menu quickly (INTENS), is not logged OUT. We have already setting an "indefine" idle time out in tcp profile, and we have also tried giving an idle time out of more than 5 minutes, but the application is still logged out when we accessed less than 1 minute if idle. AnyOne Help for this case??