Set-cookie on every http get response

[gobinathd]

Folks I am new to this forum, have a question on the http header we see ACE-LB is setting set-cookie value being set on every http get response though http get request comes with a valid cookie and valid rserver same cookie has been set on get response is that normal or any impact on this?

Any idea what is causing this behaviour? Is that something to do with Persistant Rebalance Param Map, what exactly this will do?

Is there any impact if the same cookie is being sent as "set-cookie" header tag again and again for all response to same client?

here is the config

class 204.xxx.xxx.xx-80_CLASS

    loadbalance vip inservice

    loadbalance policy 204.xx.xx.xx-80_POLICY

    loadbalance vip icmp-reply

    appl-parameter http advanced-options APP1_PARAM_MAP

  class 204.xx.xx.xx-443_CLASS

    loadbalance vip inservice

    loadbalance policy 204.xx.xxx.xx-443_POLICY

    loadbalance vip icmp-reply

    appl-parameter http advanced-options APP1_PARAM_MAP

Thanks

[Gilles Dufour]

This is indeed the result of persistence-rebalance.

This command forces ACE to inspect every REQUEST/RESPONSE and apply the config to each of them.

Without that command, ACE only does this to the first REQUEST/RESPONSE.

This command is important if you have users behind a proxy server which is doing connection sharing.

Sending the same cookie multiple time is harmless.

Gilles.

[Sean Merrow]

Hello,

Gilles is absolutely correct in his reply, but in addition, you may want to read the section in our documentation on header modify per-request, for more information on persistence-rebalance and how it differs from header modify per-request.

While it is harmless to your connections add the cookie to every response, if it is not needed, I would recommend turning it off.

HTH,

Sean