auth_result fired twice?

Hui, It's a shame this didn't work out for you but sounds like you may have another piece in your puzzle. Maybe 310 secs is too still low for your situation but at the end of the day the sessions should terminate cleanly anyway and hence these timeouts shouldn't be invoked. We never found out why most of our customers worked correctly and only a handful consistently failed with the duplicate AUTH_RESULT. Given that the client devices were exactly the same running the same code we put it down to either their internal network configuration, their ADSL modem vendor, or their ISP, or a mixture of those, or something we just hadn't thought of. In other words we have no idea but as the 310 sec timeout change resolved the issue for these very few occurrences we stopped looking. I think Aaron is right in suggesting you open a support case as if your issue and mine are loosely related, maybe having two sets of different data may assist F5 in determining the cicumstances that causes this to happen.

 

 

Aaron, you are a brave man hunting down and reading my case notes for this. ;-)

 

 

Craig