On Tue, Sep 15, 2020 at 03:10:04AM -0400, Brad Smith wrote:
> This updates the feature flags for FreeBSD.
>
> FreeBSD 10 adds support for accept4().
>
> Enable getaddrinfo().
>
> >From the FreeBSD port / package.
Applied, thanks Brad! And sorry for missing it the first time, it simply
went out
Hi Tim,
On Mon, Sep 28, 2020 at 07:02:15PM +0200, Tim Duesterhus wrote:
> see https://github.com/haproxy/haproxy/issues/860#issuecomment-693422936
> see 0354b658f061d00d5ab4b728d7deeff2c8f1503a
>
> This should be backported as a warning to 2.2.
As a rule of thumb, it would be good to keep in min
On Mon, Sep 28, 2020 at 02:31:18PM +0200, William Lallemand wrote:
> > diff --git a/doc/management.txt b/doc/management.txt
> > index adbad95d3..42e8ddbca 100644
> > --- a/doc/management.txt
> > +++ b/doc/management.txt
> > @@ -1725,6 +1725,10 @@ new ssl cert
> >Create a new empty SSL certific
On Tue, Sep 29, 2020 at 11:26:21AM +0200, Willy Tarreau wrote:
> On Mon, Sep 28, 2020 at 02:31:18PM +0200, William Lallemand wrote:
> > > diff --git a/doc/management.txt b/doc/management.txt
> > > index adbad95d3..42e8ddbca 100644
> > > --- a/doc/management.txt
> > > +++ b/doc/management.txt
> > >
Hi Elias,
On Mon, Sep 28, 2020 at 12:51:18PM +0200, Elias Abacioglu wrote:
> Hi
>
> I'm trying to get details about some errors in one of my backends.
> Looking at the stats, there are a bunch of errors per server.
> However, when I try to get details about the errors via the stats socket.
>
> #
This reuses the known `parsing [%s:%d]:` from regular config file error
reporting.
---
src/ssl_crtlist.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/src/ssl_crtlist.c b/src/ssl_crtlist.c
index fd141fc50..f1c15e051 100644
--- a/src/ssl_crtlis
Similar to warning during the parsing of the regular configuration file
that was added in 2fd5bdb439da29f15381aeb57c51327ba57674fc this patch adds
a warning to the parsing of a crt-list if the file does not end in a
newline (and thus might have been truncated).
The logic essentially just was copie
NFP WORKSHOPS
18 Blake Street, York YO1 8QG 01133 280988
Affordable Training Courses for Charities, Schools & Public Sector
Organisations
This email has been sent to haproxy@formilux.org
CLICK TO UNSUBSCRIBE FROM LIST
Alternatively send a blank e-mail to unsubscr...@nfpmail2001.co.uk quot
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses t
On 9/29/2020 5:12 AM, Willy Tarreau wrote:
On Tue, Sep 15, 2020 at 03:10:04AM -0400, Brad Smith wrote:
This updates the feature flags for FreeBSD.
FreeBSD 10 adds support for accept4().
Enable getaddrinfo().
>From the FreeBSD port / package.
Applied, thanks Brad! And sorry for missing it the
On Wed, Sep 30, 2020 at 12:00:08AM +, stable-...@haproxy.com wrote:
> Thus the computed ideal release date for 2.2.4 would be 2020-10-11, which is
> in two weeks or less.
> Thus the computed ideal release date for 2.1.9 would be 2020-09-04, which was
> three weeks ago.
> Thus the computed ide
Hi all,
while revisiting pending issues, I've come across this one, about
the impossibility for an environment variable to produce multiple
words in the configuration:
https://github.com/haproxy/haproxy/issues/165
It can be trivially addressed by adding support for ${VAR[*]} to the
config la
Hi,
HAProxy 2.2.4 was released on 2020/09/30. It added 25 new commits
after version 2.2.3.
For once there's nothing really important, it's just a pipe flush, so most
users might be encouraged to have a look at it and consider an update when
they have nothing better to do on a rainy day.
The main
I noticed the USE_CLOSEFROM define was not being passed along like the rest
during the build.
Looking around I see this was broken with the following two commits and related
series..
BUILD: Makefile: also report disabled options in the BUILD_OPTIONS variable
http://git.haproxy.org/?p=haproxy.git;
Looks like this should be back ported to 2.0, 2.1 and 2.2.
On 9/30/2020 1:04 AM, Brad Smith wrote:
I noticed the USE_CLOSEFROM define was not being passed along like the rest
during the build.
Looking around I see this was broken with the following two commits and related
series..
BUILD: Makef
Hi,
HAProxy 2.1.9 was released on 2020/09/30. It added 59 new commits
after version 2.1.8.
This version collects 2 months of fixes, the same as those that were spread
over 2.2.3 and 2.2.4, so I won't paraphrase myself, but will just give a
quick summary.
We have fixes for the reference python SP
Hi,
HAProxy 2.0.18 was released on 2020/09/30. It added 43 new commits
after version 2.0.17.
Just like with 2.1.9, this one also collects 2 months of fixes. It does
have essentially the same fixes except for the Lua changes that allowed
all sample fetch functions and converters to be used, since
Willy Tarreau wrote:
> Hi all,
> while revisiting pending issues, I've come across this one, about
> the impossibility for an environment variable to produce multiple
> words in the configuration:
> https://github.com/haproxy/haproxy/issues/165
> It can be trivially addressed by adding suppor
18 matches
Mail list logo
