This was answered in one of the post:
--------------------------------
We only parse the http header either to find a cookie or a header name or to find a specific url...
The static parse error can occur if you have an illegal character in any of these locations.
We have removed some of the restrictions .... but we are still very strict when parsing cookies.
If a cookie value or name contains spaces, or other illegal character that triggers an error.
In order to find the exact error, you will need to capture the offending packet with a sniffer trace and then inspect the cookies.
Also note that a static parse error does not forces the connection to be closed.
We just stop parsing and fall back to the default class and perform a normall loadbalance operation (no stickyness).
---------------------------------
You can attach the capture here. I can look into it.
