I am having 4 cisco ACE blades i.e 2 pairs and I have few questions when I am trying to configure stickiness and session persistence I am facing some issues for sticky table entry size
Is there any size limitation for cookie size of HTTP header/cookie?
what if it doesn't support large header/cookie size , is there any way to get the solution for this?
can somebody tell me what thing I am missing in my configuration?
Kindly find my comments there below to your questions:
I will try these in my lab apart from this I azm having few more question in my mind
How can I Verify that the load balancer (LB) is configured to load balance jpeg files.
You can configure this
How to review the configuration of the load balancer in this situation; if the load balancer should be configured to balance requests based on the ASP.Net session id of the request or something else.
Use a sniffer like wireshark or ethreal and check the static portion of Jsession-ID (usually its 10 bytes from offset 53). Following is the config for offset53,length10
sticky http-cookie JSESSIONID stitcky1
cookie offset 53 length 10
policy-map type loadbalance first-match APP1-POLICY
How will I define the max size of HTTP header is there any configuration document availble to do this ?
As I mentioned earlier, use sniffer like wireshark or ethreal and check the size of the header for regular traffic. If its more than the default ACE value then adjust it using parameter map by using header-maxparse-length set it to
parameter-map type http APP1_PARAM_MAP
And last question how should I define the load balancer fallback configuration if the HTTP header size is exceeded to the size you have suggested.
By default packet is dropped & RST is sent by ACE for closing the connection. If you want to change this behavior then use "length-exceed continue" to allow such packets through ACE module .
If a cookie, HTTP header, or URL
exceeds the default value, the ACE drops the packet and sends a RST
(reset) to the client browser.
This behavior can be changed using "length-exceed continue", however
I dont recommend this.
Its better to increase the Header parse length to the header length expected by your app.
May be this can answer your query.
Thanks for your rating.