Alright, now I get to play really dumb. I've been using curl to test this setup- I'm assuming
curl -vkL https://<PROXY SERVER>/<REQUEST>:803 is not a proper way to allow curl to reach a different port. If it is, my logs are not picking it up. What's the best method to test using a different port? -James On Sat, Oct 8, 2011 at 2:33 AM, Willy Tarreau <[email protected]> wrote: > On Sat, Oct 08, 2011 at 12:27:09AM -0700, James Nelson II wrote: > > > I don't understand what you want to achieve this way. What > transformation > > > would haproxy apply on your traffic ? > > > > Basically, I have a dev/test environment, and I don't care how messages > get to HAProxy/my VPN server, as long as the backend server sees a https > call at the end of the day. My dev environment is dealing with non-real > data, and can be unencrypted until that endpoint. > > > > In that regard, is there any method in switching tcp ports with HAProxy? > I could assign each call with a different tcp port, and based on that direct > traffic to the correct server on 443 on the backend. > > If you're fine with an IP:port mapping, then yes, it's the easiest thing to > do. > Basically : > > listen foo1 > bind ip1:port1 > server srv1 ip2:port2 > > listen foo2 > bind ip1:port1 > server srv1 ip2:port2 > ... > listen foo2 > bind ip1:port1 > server srv1 ip2:port2 > > Regards, > Willy > > -- ----------------------- James Nelson II 630-334-0177 [email protected]
