You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by DICKEY Rob <Ro...@3ds.com> on 2021/02/16 16:08:01 UTC

[users@httpd] RE: stickysession and BalancerMember route

Ignore the default separator character comment (related to jvmRoute in TomEE connectors...)

Best Regards,
Rob DICKEY
Americas R&D Technical Customer Support Senior Manager

–––––––––––––––––––––––
Office:
rob.dickey@3ds.com
http://www.3ds.com
–––––––––––––––––––––––
DS Americas Corp. | 523 W 6th Street | Los Angeles, CA 90014 | United States


-----Original Message-----
From: DICKEY Rob <Ro...@3ds.com>
Sent: Tuesday, February 16, 2021 7:52 AM
To: users@httpd.apache.org
Subject: [users@httpd] stickysession and BalancerMember route

EXTERNAL EMAIL : The sender of this email is external to 3DS. Be wary of the content and do not open unexpected attachments or links. If you consider this email as spam, you can click the following link https://spam-report.3ds.com/?linktext=https://www.mailcontrol.com/sr/ialEqMkhAmLGX2PQPOmvUtzroFmuoUEuPQhadcgl_RLXvtIKmWR8wBQF35zYCRzmUq8M6f4RkrQAXoNDtAu6BA==  (no login or additional action will be requested).


I am observing problems with mod_proxy_balancer's sticky session handling when either the length of the route attribute of the BalancerMember is > x length, or the route attribute includes any character other than [0-9][a-z][A-Z].  Note the default separator character (.) is in play.  The source code appears to perform basic string comparisons to match the stickysession token value against the route, but are there character or length constraints to the route attribute?

I am using 2.4.29+ variants.

Thanks!
Rob

This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged.

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email and all attachments,

(iii) Dassault Systèmes does not accept or assume any liability or responsibility for any use of or reliance on this email.


Please be informed that your personal data are processed according to our data privacy policy as described on our website. Should you have any questions related to personal data protection, please contact 3DS Data Protection Officer at 3DS.compliance-privacy@3ds.com<ma...@3ds.com>


For other languages, go to https://www.3ds.com/terms/email-disclaimer
This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged.

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email and all attachments,

(iii) Dassault Systèmes does not accept or assume any liability or responsibility for any use of or reliance on this email.


Please be informed that your personal data are processed according to our data privacy policy as described on our website. Should you have any questions related to personal data protection, please contact 3DS Data Protection Officer at 3DS.compliance-privacy@3ds.com<ma...@3ds.com>


For other languages, go to https://www.3ds.com/terms/email-disclaimer