i have few questions regarding the "connection" tab in HTTP(s) routing properties, which i could not figure out based on docops.
your response will be much appreciated,
1. based on your answer above, so what does the fail over strategy of "ordered/random sticky with fail over" does ? how it works and maintains sticky / session affinity ?
2. so i cannot use sticky session / session affinity when routing to HTTPs backend ? only HTTP ?
Sorry, I just realized I confused "sessions" with users too and thought you meant "user sessions". To clarify, as I understand it, it tracks based on TCP session ID which is how session affinity works across pretty much any product that communicate over TCP. In other words, it is done at the TCP layer, not the user application layer. Yes, you can use this with HTTPS.
Reference: Create Routing Strategy Assertion - CA API Gateway - 9.3 - CA Technologies Documentation
In response to your questions:
Hi Stephen / Dustin,
As suggested, I have tried to configure a context variable/CWP for the Route via HTTP(s) assertion that would take a list of URLs instead of having to set them manually hard coded via the connection tab. However,
When setting it to a multi valued context variable (containing multiple URLs) all the values get set as a single URL during execution and fails.
I was really hoping to be able to populate the multiple urls property via a single parameter/cluster property that is a list, and same for multiple IPs as a list since currently it's the main request of our customer.
i found an older communities post with a similar question as mine : Route via HTTP(s) assertion
Hopefully you can walk me through for resolving it.
Thanks Guys for the clarification. this information is very helpful