Forum Discussion
cookie persistence issue with two BiG-ip
configured with default Cookie
Hi,
Ok, so the next step is to create a new custom cookie profile for testing the different types of cookie persistence to fit them according to your application:
- HTTP Cookie Insert
Using the HTTP Cookie Insert method, the information about the server to which the client connects is inserted in the HTTP header of the response from the server in the form of a cookie. By default, the cookie is named BIGipServer<pool_name> and includes the encoded address and port of the server handling the connection. The system sets the expiration date for the cookie based on the Expiration setting in the cookie persistence profile. HTTP Cookie Insert is the default value for the Cookie Method setting.
- HTTP Cookie Passive
Using the HTTP Cookie Passive method is unlike the other cookie persistence methods. The BIG-IP system does not insert or search for blank Set-Cookie headers in the response from the server. This method does not try to set up the cookie. With this method, the server provides the cookie, formatted with the correct server information and timeout.
- HTTP Cookie Rewrite
Using the HTTP Cookie Rewrite method, the BIG-IP system intercepts a Set-Cookie header, named BIGipCookie, sent from the server to the client, and overwrites the name and value of the cookie. The new cookie is named BIGipServer<pool_name> and it includes the address and port of the server handling the connection.
In the link below you can find the way to create the cookie persistence:
- AmmarApr 17, 2022Nimbostratus
Dear
i try but not working
- Apr 18, 2022
Hi,
I recommend you open a support case, if the behavior doesn´t change it could be a bug.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com