I figured out the Apache to allow only certain traffic. Good to go there. I'm still curious on how Pound decides on which back end server to send requests to. I know it must be based on some configuration, but what configuration, I'm curious still.
Thanks Anne -----Original Message----- From: Anne Moore [mailto:[email protected]] Sent: Sunday, April 25, 2010 10:02 PM To: [email protected] Subject: RE: [Pound Mailing List] How to make user stay on the Pound Load Balancer? Jake, thank you for this explanation. I've tried to allow only traffic from the Apache BE servers, but so far, no luck. I'll keep trying though. I know there is a way with perl. Do you know how pound proxy decides on which BE server to forward the request to? Is it totally random as far as you know? Thanks Anne -----Original Message----- From: Jacob Anderson [mailto:[email protected]] Sent: Sunday, April 25, 2010 9:40 PM To: [email protected] Subject: RE: [Pound Mailing List] How to make user stay on the Pound Load Balancer? Hi Anne, This is an application problem, not a pound problem. Your application is redirecting users to the "back end" URLs instead of using the common JavaApp URL. Make your developers change their redirects to always use the common URL that hits pound instead of using the individual BE URLs. THEN, you configure the BE servers to ONLY accept HTTP/HTTPS traffic from the pound load balancer and block everyone else. That will ensure that everyone uses pound instead of being redirected. Remember that pound is a reverse proxy, not a round-robin redirector. It looks like there is a round-robin (DNS?) redirector in your loop that is directing users to individual back ends. -- jake -----Original Message----- From: Anne Moore [mailto:[email protected]] Sent: Sunday, April 25, 2010 1:19 PM To: [email protected] Subject: [Pound Mailing List] How to make user stay on the Pound Load Balancer? Hi All, I'm running Pound now in our production. However, we just realized a major problem that we can't seem to resolve. Whenever a user exits out of our Java application, they are removed from the Pound Load Balancer. For instance, They are on this Pound server URL: https://www.myPoundLB.com/JavaApp But when they exit out of the "JavaApp", they are then on one of the backend servers: http://www.backendServer1.com/my/JavaApp This, as you can see, creates big problems. They are no long on SSL, and they are off of Pound Load Balancer. Unfortunately, I cannot do a re-direct on the backend servers, because that creates a loop with the Pound Load Balancers. Is there any way with Pound, to configure it that they absolutely stay on the Pound LB the entire time? Thank you for your help! Anne -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
