tortoiseSVN client errors out on some commits

I'm not too happy leaving caching at 0

 

I am not happy either that I can't explain why the LTM is behaving this way, and that makes the LTM look bad. I have seen mention of TLS-related bugs - I'm wondering if this is somehow related. But I'm not enough of a TLS/SSL expert to diagnose what's happening. To me, it simply looks like the client is attempting to establish a SSH session with valid Session ID, and the LTM is ignoring it. I'm running 10.2.0. Maybe someone else with a bit more TLS knowledge can weigh in.

 

 

The question of impact to your main VIPs is really a dependent on your environment. To give you some context, my busiest LTM pair (6900) averages a sustained 100 SSL TPS, 400-500k active connections, and ~800 HTTP requests/sec, with ~500 :443 VIPs (~1200 total). But our TortoiseSVN user base is a small group of people, so the impact of disabling SSL session cache for their one SSL VIP is minimal. What is more of a headache for me is managing its customized Client SSL Profile.