Le 6/16/22 à 05:12, David Leadbeater a écrit :
I tried upgrading to 2.6.0 (from 2.5.6) and I'm seeing a segfault when
making HTTP/2 requests. I'm using a frontend in TCP mode and then
switching it to HTTP/2.
I've made a minimal config that exhibits the segfault, below. Simply
doing curl -vk http
On Thu, 16 Jun 2022 20:49:00 +1000
David Leadbeater wrote:
> On Thu, 16 Jun 2022 at 20:27, Aleksandar Lazic wrote:
> [...]
> > > Thanks ! I'm able to reproduce the segfault. I'm on it.
>
> Thanks!
>
> > But in any way wouldn't be better that the rule
> >
> > acl ipwtf hdr(Host),lower,field(1,:
On Thu, 16 Jun 2022 at 20:27, Aleksandar Lazic wrote:
[...]
> > Thanks ! I'm able to reproduce the segfault. I'm on it.
Thanks!
> But in any way wouldn't be better that the rule
>
> acl ipwtf hdr(Host),lower,field(1,:),word(-1,.,2) ip.wtf
>
> be after
>
> > >tcp-request inspect-delay 10s
> >
On Thu, 16 Jun 2022 10:22:30 +0200
Christopher Faulet wrote:
> Le 6/16/22 à 05:12, David Leadbeater a écrit :
> > I tried upgrading to 2.6.0 (from 2.5.6) and I'm seeing a segfault when
> > making HTTP/2 requests. I'm using a frontend in TCP mode and then
> > switching it to HTTP/2.
> >
> > I've
Le 6/16/22 à 05:12, David Leadbeater a écrit :
I tried upgrading to 2.6.0 (from 2.5.6) and I'm seeing a segfault when
making HTTP/2 requests. I'm using a frontend in TCP mode and then
switching it to HTTP/2.
I've made a minimal config that exhibits the segfault, below. Simply
doing curl -vk http
I tried upgrading to 2.6.0 (from 2.5.6) and I'm seeing a segfault when
making HTTP/2 requests. I'm using a frontend in TCP mode and then
switching it to HTTP/2.
I've made a minimal config that exhibits the segfault, below. Simply
doing curl -vk https://ip is enough to trigger it for me.
Thread 1
6 matches
Mail list logo