I will need to look at your suggestion some more to understand how it will pass 443 traffic to the backend server, I only see definitions for port 80. Since I am using pfsense and the haproxy package I will also have to figure out how to define peers as that does not seem to be available in the web gui.
thanks On Mon, Oct 12, 2015 at 8:22 AM, Baptiste <bed...@gmail.com> wrote: > So basically, here is what you want to do: > peers mypeers > # read the doc for the info to store here > > frontend ftapp > bind :80 > bind :443 > mode tcp > default_backend bkapp > > backend bkapp > mode tcp > stick-table type ip size 10k peers mypeers > stick on src > server s1 a.b.c.d check port 80 > server s2 a.b.c.e check port 80 > > > Baptiste > > > On Mon, Oct 12, 2015 at 4:40 PM, Daren Sefcik <dsef...@hightechhigh.org> > wrote: > > humm...not sure I know how to answer that...we have servers that require > SSL > > for some requests and not for others. I am not needing to do anything > other > > than pass the traffic along, not doing any inspection or verifying of > cert > > or anything. I tried to setup a frontend with 2 servers in the backend, > one > > with 443 and the other with 80 but that didn't seem to work, like it > would > > pick the wrong one to send to. > > > > On Mon, Oct 12, 2015 at 7:29 AM, Baptiste <bed...@gmail.com> wrote: > >> > >> Hi Daren, > >> > >> Do you want/need to decipher the traffic when using SSL? > >> > >> Baptiste > >> > >> On Mon, Oct 12, 2015 at 4:24 PM, Daren Sefcik <dsef...@hightechhigh.org > > > >> wrote: > >> > I am probably totally overlooking something but how do I configure a > >> > frontend/backend to pass to the same server for both SSL and Non SSL > >> > requests? We have server that require ssl for some applications but > >> > most of > >> > the time not. > >> > > > > > >
