Thanks - I found that 64 limit in code, and did not look like any other 
character in the route string match would be problematic but for a route value 
like route=ab-8080-cde1 we are finding that stickiness is not consistent... the 
preamble to the route is another string like WebAppName.ab-8080-cde1 but in all 
cases the separator character is present...and the client is being sent and 
presenting the stickiness cookie as expected.

When we modify the route to be simple like route=a80801 the stickiness works as 
expected.

I'll keep debugging.

Thanks.

Rob

-----Original Message-----
From: Yann Ylavic <ylavic....@gmail.com>
Sent: Wednesday, February 17, 2021 9:21 AM
To: users@httpd.apache.org
Subject: Re: [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/sb0m7JMjc8HGX2PQPOmvUnWvS4wCa9RdYx4S0Ab4cVyGh1Lme3UWvhQF35zYCRzmptrco86Du5j3vm7b4Ic-_w==
  (no login or additional action will be requested).


On Tue, Feb 16, 2021 at 4:52 PM DICKEY Rob <rob.dic...@3ds.com> wrote:
>
> 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?

The route is limited to 64 characters and must be preceded by a special 
character within the URL/cookie value (default character is '.', though 
stickysessionsep= might be used to change it). These are the only constraints 
I'm aware of..

But this means that the backend must set routed URLs/cookies of that form, 
otherwise some "automatic" routing can be performed like in 
https://httpd.apache.org/docs/2.4/en/mod/mod_proxy_balancer.html#example
(the one using mod_headers).

Regards;
Yann.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

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-priv...@3ds.com<mailto:3ds.compliance-priv...@3ds.com>


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

Reply via email to