Forum Discussion
ASM adding unwanted cookie
Hi, we have a VS created in LTM with Default Persistence as universal & following iRule:
when HTTP_REQUEST {
if { [string tolower [HTTP::path]] starts_with "/abcd" } {
pool Pool1
} else {
set jsess [URI::query [HTTP::uri] PARAM]
if { $jsess != "" } {
persist uie $jsess 600
pool Pool2
}
}
}
However, we are getting one unwanted cookie in response, so is it possible that above combination will add some unwanted default cookie for response?
28 Replies
- Pranav_73262
Nimbostratus
Modified question to reflect exact issue for the benefit of future references.
- Romain_Dayan_83
Nimbostratus
Hi,
What is you ASM deployment mode ? If you can isolate this application on another security policy you can disable the ASM cookie feature only in this case.
I can warn you that the "TS*" cookie can be in lower case sometime but I don't know what will be the behavior of the ASM if the cookie is not present and the feature enabled.
- Pranav_73262
Nimbostratus
Hi Romain, how to disable ASM cookie? I checked all options available; but no luck. At max it allows us to play with expiration timer, MD5 hash etc.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com