matchclass, uri routing, and cookie persist & snat irule

Hey Aaron - I just read your note on OneConnect above. I will definitely give the profilei a go. And I have a few more questions to help clear up my thought process. I really appreciate all of your info!

 

 

So I believe the vendor said we should key off of the various JSESSIONID cookies to ensure proper persistence. That said, I'm sure a persistence cookie manual insert may work just the same. However, for now, I'd like to try your iRule above, and just want to confirm that I understand how it flows. So I've summarized my comprehension below - please clarify if necessary.

 

 

1. For every incoming HTTP request, the LTM switches the path to lower for iRule evaluation. if it sees any of the matching URI paths, it next sets a variable called cookie_name to have a value of the corresponding JSESSIONID cookie.

 

 

2. Next the LTM confirms the existence of the actual cookie and, if found, will use it as the persistence mechanism.

 

 

3. Finally, any outbound HTTP server responses that may be setting persistence cookies will be captured and recorded by the LTM to ensure future requests go back to the correct pool member.

 

 

Does that sound about right?

 

 

Thanks,

 

Brian