Re: OpenSSL Security Advisory

Thanks for all of the responses! So the image version number for HAProxy stays the same but the hash will update? > On Mar 25, 2021, at 9:03 AM, Tim Düsterhus wrote: > > Paul, > > On 3/25/21 4:46 PM, Paul Lockaby wrote: >> As a lurker on this list I've always kind of won

Re: OpenSSL Security Advisory

Hello! As a lurker on this list I've always kind of wondered what the policy is for releasing new containers to address security patches on dependencies like this. I'm not sure who maintains the "official" containers for HAProxy but would they do a re-release of the latest versions to include

Re: directing requests to a specific server

Perfect! Thanks Tim. So many options in the HAProxy configuration sometimes I get lost in it. > On May 23, 2019, at 12:09 PM, Tim Düsterhus wrote: > > Paul, > > Am 23.05.19 um 20:17 schrieb Paul Lockaby: >> If there is a way that I can direct a request to a specific se

directing requests to a specific server

Hello! I have a frontend/backend that looks kind of like below, obviously very simplified. frontend myhost-frontend bind *:443 ssl crt /usr/local/ssl/certs/host.pem mode http log global acl request_monitor_cluster path_beg /monitor/cluster use_backend monitor_cluster if

Re: Is it possible to configure a failover backend?

Yes. Whichever backend server you do not want to route requests to except when the primary server is offline, append the keyword "backup" to that server's configuration (after the word "check"). E.g.: server loggingdc1-elasticsearch-05a:9200 10.1.20.25:9200 check backup -Paul > On Jan 29,

Re: problem in 1.8 with hosts going out of service

This patch works for me. Thank you! > On Jan 24, 2018, at 1:02 PM, Christopher Faulet <cfau...@haproxy.com> wrote: > > Le 24/01/2018 à 17:21, Paul Lockaby a écrit : >> Sorry, I know this list is super busy and that there are a number of other >> more important is

Re: problem in 1.8 with hosts going out of service

Sorry, I know this list is super busy and that there are a number of other more important issues that need to be worked through but I'm hoping one of the maintainers has been able to confirm this bug? Thanks, -Paul > On Jan 17, 2018, at 10:27 AM, Paul Lockaby <plock...@uw.edu> wrote

Re: problem in 1.8 with hosts going out of service

m 1.7 because I used this feature in 1.7 without issue. > On Jan 16, 2018, at 10:36 PM, Paul Lockaby <plock...@uw.edu> wrote: > > I'm experiencing a problem that I can't diagnose but I can recreate pretty > consistently. I have a single server that responds for example.com and

problem in 1.8 with hosts going out of service

I'm experiencing a problem that I can't diagnose but I can recreate pretty consistently. I have a single server that responds for example.com and api.example.com and it runs haproxy. All the names run through an SSL front door but an ACL makes it such that requests for example.com get sent to

Re: disable-on-404 functionality change in 1.8

> On Dec 23, 2017, at 2:24 AM, Willy Tarreau wrote: > > Hi guys, > > On Sat, Dec 23, 2017 at 08:58:43AM +0100, Cyril Bonté wrote: >> It looks to be a code regression. >> >> Emeric, can you have a look at commit 5a1335110c ? It seems there was an >> unwanted change in the

disable-on-404 functionality change in 1.8

goes to "active or backup DOWN". But the change from 1.7 to 1.8 was jarring and surprising and I did not see anything in the changelog indicating that this is supposed to have changed like this. Was I doing it wrong from the beginning? Thank you for your help. Paul Lockaby