On Wed, Dec 12, 2018 at 11:00:21AM -0700, Sean Reifschneider wrote:
> Thanks, that makes sense and I did a quick test with just the Host header
> based routing and that was looking good. I don't recall where I got to
> both SNI and host selection, that might be something that fixed a problem 3
>
Thanks, that makes sense and I did a quick test with just the Host header
based routing and that was looking good. I don't recall where I got to
both SNI and host selection, that might be something that fixed a problem 3
years ago, or might have just been my misunderstanding.
Thanks!
Sean
On
Hi Sean,
On Tue, Dec 11, 2018 at 04:22:53PM -0700, Sean Reifschneider wrote:
> I've been trying to convert my haproxy setup (1.8.14) to by adding "alpn
> h2,http/1.1" to my "bind" line in the frontend. My haproxy config is north
> of 300 lines, so I'll hold off on attaching it.
>
> My frontend
I've been trying to convert my haproxy setup (1.8.14) to by adding "alpn
h2,http/1.1" to my "bind" line in the frontend. My haproxy config is north
of 300 lines, so I'll hold off on attaching it.
My frontend selects backends using something like:
acl aerial_acl hdr(host) -m reg -i
4 matches
Mail list logo
