Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi,I have a vserver configured with a SLB policy and persistent rebalance. The policy uses a sticky based on JSESSIONID cookie. If my clients HTTP traffic comes in HTTP1.0, I have no problems; if it comes in HTTP1.1 I have problems. Sniffing the traf...
Suppose two users A and B.If B send info encrypted with A's public key, only A can decrypt the info because he is the only one with it's private key. But if A send info encrypted with it's own private key, anyone with A's public key can decrypt the i...
Thanks for your reply.Before sharing the trace, can you please explain how "the connection is simply balanced", mainly for HTTP1.1?Even without the cookie presence at HTTP packets, I get polity matches on CSM (default policy scores 0 matches). Why?Re...
Thank you for your reply.As I can see from your writting, each user should have one private key for each communication partner. Each of these keys "have" associated public keys.So, the "public key" can be public not for public use (more than 1 user) ...
What you are telling me is that if A wants to communicate with B he should use B's public key and for B->A, B should use A's public key. So each user must have a public key for each partner he wants to communicate with?Regards,JPL
