--> In the last post, I have discussed the introduction to cookies and Cookie Insert Method. In this Blog Post, I will discuss the other methods being used in Cookie Persistence:
2) Cookie Rewrite:
--> The First HTTP request will be load balanced to select the pool member according to the load balancing algorithm.
--> When the selected Pool member sends the HTTP response as well as cookie through F5 BIG IP System then the Cookie value sent by the pool member will be modified by F5 before sending the response to the client.
--> Client stores the Cookie Value in the Browser and When the client sends a new HTTP request then the cookie value is also sent in addition to an HTTP request by the client.
--> The F5 LTM sees the cookie value in the HTTP request and accordingly selects the pool member mentioned in the cookie.
--> Now all the traffic from the same client will be sent to the selected pool member in the cookie, Load Balancing does not happen after initial HTTP request.
--> configuration changes are required on the Backend server to use Cookie Rewrite Method.
--> Blank Cookie need to be created in a specific format on the Web Server
--> Persistence Mirroring need not be enabled as the Cookies are getting stored on the Client Browser and even failover happens the client request will go to the exact pool member.
--> The system sets the expiration date for the cookie based on the Expiration setting in the cookie persistence profile.
3) Cookie Passive
--> The First HTTP request will be load balanced to select the pool member according to the load balancing algorithm.
--> When the selected Pool member sends the HTTP response as well as cookie through F5 BIG IP System then Cookie value sent by the server will not be modified by F5 before sending the response to the client.
--> Client stores the Cookie Value in the Browser and When the client sends a new HTTP request then the cookie value is also sent in addition to an HTTP request by the client.
--> The F5 LTM sees the cookie value in the HTTP request and accordingly selects the pool member mentioned in the cookie.
--> Now all the traffic from the same client will be sent to the selected pool member in the cookie, Load Balancing does not happen after initial HTTP request.
--> configuration changes are required on the Backend server to use Cookie Passive Method.
--> Cookie need to be created in on the Web Server
--> Persistence Mirroring need not be enabled as the Cookies are getting stored on the Client Browser and even failover happens the client request will go to the exact pool member.
--> The system sets the expiration date for the cookie based on the Expiration setting in the cookie persistence profile.
4) Cookie Hash
--> The First HTTP request will be load balanced to select the pool member according to the load balancing algorithm.
--> When the selected Pool member sends the HTTP response as well as cookie through F5 BIG IP System then Cookie value sent by the server will be modified by F5 before sending the response to the client.
--> The F5 LTM calculates the hash value of the cookie and sends the hash value is stored under the persistence table of the F5 LTM.
--> Client stores the Cookie Value in the Browser and When the client sends a new HTTP request then the cookie value is also sent in addition to an HTTP request by the client.
--> The F5 LTM sees the cookie value in the HTTP request and calculates the Hash value and accordingly selects the pool member stored in the persistence table.
--> Now all the traffic from the same client will be sent to the selected pool member in the cookie, Load Balancing does not happen after initial HTTP request.
--> configuration changes are required on the Backend server to use Cookie Passive Method.
--> Cookie need to be created in on the Web Server
--> Persistence Mirroring need be enabled as the Hash values of Cookies are getting stored on the Persistence Table and when failover happens the client request will go to exact pool member if the persistence table is mirrored to the standby F5.
--> The system sets the expiration date for the cookie based on the Expiration setting in the cookie persistence profile.
Reference: F5.com
Md.Kareemoddin,
CCIE # 54759
Super Duper Explanation
ReplyDelete