During a cookie issues involving passing through 2 CSS units I opened a Tac Case.
During this case , I was advised to use the flow timout multiplier command as a possiblity in resolving the cookie issue.
Unique names on the cookie seemed to cure the issue. But, I did leave the flow timeout multiplier on the rule.
This has worked for well for many months.
above this CSS are a pair of proxies that take care of external access. These proxies are having problems under load. The logs from these proxies seem to indicate that sessions are staying open, TCP 3 way handsahake don't always close correctly etc.
My question is Do I really need the flow timeout multiplier set to 120 ( default 8 for http ) Is this contributing to the issue. Below is a cleaned up content rule
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...