application ssl

[skumar1969]

I am wondering where would we be using this command application ssl.

CCO docs says use it if you want to take advantage of the ssl session id stickiness reuse and multiple ssl modules.

However I am not using both these features I mean single ssl module and arrow-point stickiness but still I need this command to make SSL termination to work. It seems the usage is pretty mandatory.

Anyone know why? Much appreciated if someone could respond.

[Gilles Dufour]

the command tells the CSS how to interpret the data that it is receiving.

So, as the documentation says, the only itme you need to interpret SSL data is if you want to do SSL stickyness.

With one module there is no need to do stickyness.

arrowpoint cookie stickyness comes after SSL termination on the decrypted content rule.

this content rule should not use the 'application ssl' command.

In your case there is really no need for this command.

If the config does not work once you remove it, there must be an error somewhere in the config. You can send it to us if you want a free analysis :-)

Gilles.