Sticky http cookie xxx that you have configured is for the cookie inside HTTP Header. It looks like you want the ACE to read the cookie from URL and ace can do that. Please have a look at "Secondary Cookie" option.
The way this typically works is that server is configured to insert the same secondary cookie in both the "Set-Cookie" header and HTML URI. ACE creates a sticky entry based on the Set-Cookie header of the server response. Then, when client returns with the same cookie value in the URL query, it is stuck to the same server.
"Cookie secondary" is not meant to work independently of regular cookies. It is meant to be a complementary feature for cases where the client has disabled cookies in their browser. The server is still expected to insert a standard Set-Cookie header in the response.
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast by Friday, December 3.
To learn what's new in this year's competition or to gain insights into the judging considerations, check out ...
Data Center and Cloud Networking News
Cisco Nexus Dashboard Open Ecosystem with Splunk
End-to-End Flow State Validation with Nexus Dashboard Insights Connectivity Analysis
Cisco Q1 NPI Announcements for Data Center and Cloud Networking
We delivered a partner enablement training session in September 2021 to share the ACI upgrade Best Practices.
The slide deck is enclosed here for wider audience in the community, it provides more details in terms of the best practices, tools and co...
What is Cisco ACI Anywhere?What are ACI connectivity options for managing Primary On-Prem DCs?What are ACI options for extending your Data center to secondary remote locations (Physical)?How ACI provides centralized network policy framework for workloads ...
Cloud Networking Community on Cisco Customer Connection
Join our community!!
As a valued Cisco Cloud Networking (former DCN) customer, you can be part of Cisco Customer Connection Program (CCP), Cisco’s global online community program. Connect ...