irule for implementing hash persistency

Hi,

when HTTP_REQUEST {
    persist hash [HTTP::header myheader]
}

Thanks, Stephan

Thnaks a lot Stephan,

it really helps . let me get in touch with Application team and get the required info.

I will contact you in case i need any other help after the information provided by application team.

HI Stephan,

Application responded as below

Unique Identifier value is “1” on both the servers WEB07 & WEB08 and there is no header value configured.

So in this case if I add below irule will it work for Hash?

when HTTP_REQUEST { persist hash [HTTP::header "1"] }

Hi Stephan,

One quick question

HTTP Cookie Insert method

If you specify HTTP Cookie Insert method within the profile, the information about the server to which the client connects is inserted in the header of the HTTP response from the server as a cookie. By default, the cookie is named BIGipServer, and it includes the encoded address and port of the server handling the connection. The expiration date for the cookie is set based on the timeout configured in the persistence profile. HTTP Cookie Insert is the default value for the Cookie Method setting.

Just wanted to understand if I use this will F5 insert cookie ? as you know the application is not using any header in the browser/

HI stephan,

Just got another hurdle , please find below mail

This is the solution given to end user

HI Robert ,

We don;t need to modify anything on client or server level for configuring cookie persistency. We required those information only if we insists to Use Hash persistency which we are currently using and not working as expected.

If we use cookie persistency F5 will insert cookie in client browser . and there is no need of any modification on client or server end. Please find below information about cookie insert method. This will make sure the user will be sent to same server as long as his session is valid . For new incoming traffic load balancing will work based on load balancing method ( roundrobin) .

HTTP Cookie Insert method If you specify HTTP Cookie Insert method within the profile, the information about the server to which the client connects is inserted in the header of the HTTP response from the server as a cookie. By default, the cookie is named BIGipServer, and it includes the encoded address and port of the server handling the connection. The expiration date for the cookie is set based on the timeout configured in the persistence profile. HTTP Cookie Insert is the default value for the Cookie Method setting.

Regards, Kaladhar

I agree, this would probably work for users accessing the website using web browsers.

But web service client (SOAP) applications will not necessarily read the cookie header and/or pass the cookie back. Existing applications will almost certainly need to be updated to specifically do this.

? Wouldn’t the web services not need persistence at all? The only sites we have that need to worry about the cookies would be the ones that use that report control.

No, that's correct. The web services don't need persistence at all. We WANT those requests to be distributed across both web servers.

Can we add an irule that users hitting vip via browser should use cookie insert and all other request should use Source address persistence ?

if yes please let me know if u have any similar irule handy

HI stephan,

Just got another hurdle , please find below mail

This is the solution given to end user

HI Robert ,

We don’t need to modify anything on client or server level for configuring cookie persistency. We required those information only if we insists to Use Hash persistency which we are currently using and not working as expected.

If we use cookie persistency F5 will insert cookie in client browser . and there is no need of any modification on client or server end. Please find below information about cookie insert method. This will make sure the user will be sent to same server as long as his session is valid . For new incoming traffic load balancing will work based on load balancing method ( roundrobin) .

HTTP Cookie Insert method If you specify HTTP Cookie Insert method within the profile, the information about the server to which the client connects is inserted in the header of the HTTP response from the server as a cookie. By default, the cookie is named BIGipServer, and it includes the encoded address and port of the server handling the connection. The expiration date for the cookie is set based on the timeout configured in the persistence profile. HTTP Cookie Insert is the default value for the Cookie Method setting.

Regards, Kaladhar

I agree, this would probably work for users accessing the website using web browsers.

But web service client (SOAP) applications will not necessarily read the cookie header and/or pass the cookie back. Existing applications will almost certainly need to be updated to specifically do this.

Reply 2 ? Wouldn’t the web services not need persistence at all? The only sites we have that need to worry about the cookies would be the ones that use that report control.

Reply3 No, that's correct. The web services don't need persistence at all. We WANT those requests to be distributed across both web servers.

Can we add an irule that users hitting vip via browser should use cookie insert and all other request should use Source address persistence ?

if yes please let me know if u have any similar irule handy

Hi vvskaladhar,

Yes, it's exactly the config I have in mind. :-)