Http header based persistence

Question

&nbsp;Hello,&nbsp;
&nbsp;I have the following setup to enable persistence on incoming http requests.&nbsp;
&nbsp;when HTTP_REQUEST { persist hash [HTTP::header "Y-ABC-UserID"] } &nbsp;
&nbsp; The goals is to to have a user who's user id is appended as such &nbsp;
&nbsp;"Y-ABC-UserID:"&nbsp;
&nbsp;always persist to the node on which their connection orignally establishes based on the rules of the pool.  It is not working correctly and the users session bounces back and forth across the pool.&nbsp;
&nbsp;Any one with any thoughts? all suggestions are great appreciated&nbsp;
&nbsp;Cheers&nbsp;&nbsp;&nbsp;

patrick_chang_7 · Answer

You must also have a persistence profile specified in the virtual server.

michael_yates · Answer

Hi MK, 
  
 Perhaps you should try using "persist uie" instead of persist hash. 
  
 Something like:

when HTTP_REQUEST {
  if { [HTTP::header exists "Y-ABC-UserID"] } {
    persist uie [HTTP::header "Y-ABC-UserID"]
  }
}

iRules: "persist" v. "persist add" 
 Irule for Universal Persistance Using a Header Value

Hope this helps.

nitass · Answer

just curious who generates Y-ABC-UserID header. is it client? 
&nbsp; if so, does it send the header on every request? 
&nbsp; can you post the full irule?

Forum Discussion

Http header based persistence

3 Replies

Recent Discussions

google autenticator broken barcode

Error while running ansible

ASM instance creation

[ASM] - what is "Browser Challange file" ?

[ASM] - HTML5 Cross-Domain Request Enforcement - CLI command

Related Content

Session persistence based on http header for machine to machine calls

Bot Signature based on the referer header

Persist connection based on NTLM username

Payload string based persistence

Session Persistence based on http header value using iRule