HAProxy Technologies, Using Twitter Mike makes more than a Lawyer WTF

Your email client cannot read this email. To view it online, please go here: http://www.mailmozo.com/mail/display.php?M=232681=bb5dcd9549911e7eaced94aad1cbd7db=30=24=18 And he only works 20 hours a week from all over the world! Truth or B.S.? I had to dig in and find out for myself. Here's

Re: 502 error when connection loopback to haproxy

Hi The request never reached the application server. It first reached port 80 then haproxy adds a header and sends to port localhost:81 which is also handled by haproxy. For 502 requests, they never reached port 81. On Sat, Feb 18, 2017 at 4:58 AM Dennis Jacobfeuerborn

Re: 502 error when connection loopback to haproxy

On 17.02.2017 12:42, Chungwei Yen wrote: > Hi > > I am having a strange error when sending requests back to haproxy. The > configuration is to have an additional layer of frontend/backend to > generate a unique request id for every request then redirect back to > haproxy to the real frontend. >

Re: SSL Termination or Passthrough

After looking at the config more on that page, I see this is termination with http traffic on the backend (which is what Willie said). So to keep it TLS the whole way to the back end I have to use TCP pass through. Thanks again this has been informative. Sam On February 18, 2017 at 6:51:10

Re: SSL Termination or Passthrough

Thanks, this is what I was looking for. I could just call a reload of the LB with the PID whenever the CRL was updated by the cron. Is there a requirement to bind on 443 for this method or can I make it anything? Adding the header info with the details from the client will require a backend