Re: h1-client to h2-server host header / authority conversion failure.?

2019-02-01 Thread Willy Tarreau
On Sat, Feb 02, 2019 at 12:16:27AM +0100, PiBa-NL wrote: > Sorry, indeed all 4 tests pass. ( Using 2.0-dev0-32211a1 2019/02/01 ) Ah cool, thanks! > I must have mixed the git-id to sync up with in my makefile, thought i > picked the last one.. > > Sorry for the noise! Thanks for fixing and

Re: h1-client to h2-server host header / authority conversion failure.?

2019-02-01 Thread PiBa-NL
Hi Willy, Op 2-2-2019 om 0:01 schreef Willy Tarreau: On Fri, Feb 01, 2019 at 09:43:13PM +0100, PiBa-NL wrote: The 'last' part is in TCP mode, and is intended like that to allow me to run tcpdump/wireshark on the un-encrypted traffic, and being certain that haproxy would not modify it before

Re: h1-client to h2-server host header / authority conversion failure.?

2019-02-01 Thread Willy Tarreau
On Fri, Feb 01, 2019 at 09:43:13PM +0100, PiBa-NL wrote: > The 'last' part is in TCP mode, and is intended like that to allow me to run > tcpdump/wireshark on the un-encrypted traffic, and being certain that > haproxy would not modify it before sending. But maybe the test contained a > 'half done'

Re: h1-client to h2-server host header / authority conversion failure.?

2019-02-01 Thread Willy Tarreau
Hi Pieter, I'm finally back to this one. On Sat, Jan 26, 2019 at 09:04:06PM +0100, PiBa-NL wrote: > It seems google replies "Header: :status: 400 Bad Request" But leaves me > 'guessing' why it would be invalid, also the 'body' doesn't get downloaded > but haproxy terminates the connection, which

Re: h1-client to h2-server host header / authority conversion failure.?

2019-01-30 Thread Willy Tarreau
On Wed, Jan 30, 2019 at 10:37:29AM +0100, Willy Tarreau wrote: > > It seems google replies "Header: :status: 400 Bad Request" But leaves me > > 'guessing' why it would be invalid, > > Interesting case. Actually we're doing something wrong, and we cannot rule out that it's why google is upset.

Re: h1-client to h2-server host header / authority conversion failure.?

2019-01-30 Thread Willy Tarreau
Hi Pieter, On Sat, Jan 26, 2019 at 09:04:06PM +0100, PiBa-NL wrote: > Today ive given it another shot. (connecting to mail.google.com). > Is there a way in haproxy to directly 'manipulate' the h2 headers? Setting > h2 header with set-header :authority didn't seem to work.? No, these ones are

Re: h1-client to h2-server host header / authority conversion failure.?

2019-01-28 Thread Willy Tarreau
Hi Pieter, On Mon, Jan 28, 2019 at 07:44:55PM +0100, PiBa-NL wrote: > Hi Willy, List, > > Just a little check, was below mail received properly with the 6 attachments > (vtc/vtc/log/png/png/pcapng) .? > (As it didn't show up on the mail-archive.) Yes, I can confirm I received it both directly

Re: h1-client to h2-server host header / authority conversion failure.?

2019-01-28 Thread PiBa-NL
Hi Willy, List, Just a little check, was below mail received properly with the 6 attachments (vtc/vtc/log/png/png/pcapng) .? (As it didn't show up on the mail-archive.) Regards, PiBa-NL (Pieter) Op 26-1-2019 om 21:04 schreef PiBa-NL: Hi Willy, Op 25-1-2019 om 17:04 schreef Willy Tarreau:

Re: h1-client to h2-server host header / authority conversion failure.?

2019-01-25 Thread Aleksandar Lazic
Hi List. Am 25-01-2019 01:01, schrieb PiBa-NL: Hi List, Attached a regtest which i 'think' should pass. **   s1    0.0 === expect tbl.dec[1].key == ":authority" s1    0.0 EXPECT tbl.dec[1].key (host) == ":authority" failed It seems to me the Host <> Authority conversion isn't happening

Re: h1-client to h2-server host header / authority conversion failure.?

2019-01-25 Thread Willy Tarreau
Hi Pieter, On Fri, Jan 25, 2019 at 01:01:19AM +0100, PiBa-NL wrote: > Hi List, > > Attached a regtest which i 'think' should pass. > > **   s1    0.0 === expect tbl.dec[1].key == ":authority" > s1    0.0 EXPECT tbl.dec[1].key (host) == ":authority" failed > > It seems to me the Host <>

h1-client to h2-server host header / authority conversion failure.?

2019-01-24 Thread PiBa-NL
Hi List, Attached a regtest which i 'think' should pass. **   s1    0.0 === expect tbl.dec[1].key == ":authority" s1    0.0 EXPECT tbl.dec[1].key (host) == ":authority" failed It seems to me the Host <> Authority conversion isn't happening properly.? But maybe i'm just making a mistake