Forum Discussion
NimbostratusASM 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_73262TMOS is v11.3- Pranav_73262We have LTM & ASM on same appliance.
Michael_KoyfmanCirrocumulus
Are you getting an ASM violation with respect to cookie? If so, please advise what is the violation/cookie name that is being complained about. The iRule itself as you posted does not do any cookie manipulation/addition/deletion.
- Pranav_73262No violations in ASM. Request is going through. will Default Persistence profile of universal ass any cookie?
- Pranav_73262Also is there any way to troubleshoot this e.g. enabling request logging etc.
Michael_Koyfma1Cirrus
Are you getting an ASM violation with respect to cookie? If so, please advise what is the violation/cookie name that is being complained about. The iRule itself as you posted does not do any cookie manipulation/addition/deletion.
- Pranav_73262No violations in ASM. Request is going through. will Default Persistence profile of universal ass any cookie?
- Pranav_73262Also is there any way to troubleshoot this e.g. enabling request logging etc.
- boneyard
MVP
what is the cookie name? it might be the ASM one, which is there for a reason. - Pranav_73262TSc096fc
- Pranav_73262It looks like a ASM cookie. ASM Main Cookie, can we disble it in response to client?
- boneyardyes that is certainly an ASM cookie, never took the time to find out if you can remove it with an iRule, you could give it a try.
- Pranav_73262
Hi
I am trying following iRule:
when HTTP_RESPONSE_RELEASE { set cookies [HTTP::cookie names] foreach aCookie $cookies { if {$aCookie starts_with "TS"} { HTTP::cookie remove $aCookie } } } Is this correct one? - Michael_Koyfman
You will break ASM functionality if you remove TS cookie. Is the cookie that ASM sends affecting the client behavior? That should not be the case. If yes, is this a browser or a custom client?
- Pranav_73262Ok. Actually it is not affecting client behavior, however, customer has requirement that we should not send any cookies. It is HTTPS application.
- boneyardjust thinking out loud, is ASM required?
- Pranav_73262yes, it is required. But should not add cookie :) only inspect and block in case of violations.
