Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

On 11/08/2016 10:05 p.m., Erik Seres wrote: > Hi Amos, > > Thanks for the answers. After a bit of a delay, I’m getting back to > implementing this. However, I still have a couple of questions in line > below... > > Thanks, > Erik > > >> On 2016 Jun 1, at 08:44, Amos Jeffries wrote: >> >> On

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

Hi Amos, Thanks for the answers. After a bit of a delay, I’m getting back to implementing this. However, I still have a couple of questions in line below... Thanks, Erik > On 2016 Jun 1, at 08:44, Amos Jeffries wrote: > > On 30/05/2016 11:03 p.m., Erik Seres wrote: >>

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

On 30/05/2016 11:03 p.m., Erik Seres wrote: > Hi Willy and Amos, > > I think I am confused by what information is expected to go into the > PP2_TYPE_AUTHORITY field and how it would be a suitable substitute > for what SNI represents. PP2 is generic and needs to relay multiple protocols.

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

Hi Willy and Amos, I think I am confused by what information is expected to go into the PP2_TYPE_AUTHORITY field and how it would be a suitable substitute for what SNI represents. Where would that information (server name?) come from outside the TLS handshake? And why is HTTP CONNECT mentioned

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

Hi Amos, On Fri, May 27, 2016 at 06:39:45PM +1200, Amos Jeffries wrote: > On 27/05/2016 2:42 a.m., Willy Tarreau wrote: > > On Thu, May 26, 2016 at 10:20:36AM -0400, Erik Seres wrote: > >> Hi Willy, > >> > >> Attached is my updated patch per your styling update request. > > > > Thanks Erik. I'm

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

On 27/05/2016 2:42 a.m., Willy Tarreau wrote: > On Thu, May 26, 2016 at 10:20:36AM -0400, Erik Seres wrote: >> Hi Willy, >> >> Attached is my updated patch per your styling update request. > > Thanks Erik. I'm now CCing Dave and Amos, both of whom worked on this > 18 months ago. Amos requested

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

.com> Date: Thu, 12 May 2016 11:05:14 +0200 Subject: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header. If the client provides the server name it intends to connect to, per RFC3546, Section 3.1. Server Name Indication, this patch will pass the server name onto

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

Hi Willy, Attached is my updated patch per your styling update request. Thanks, Erik On 2016 May 26 Thu at 08:40:00, Willy Tarreau (w...@1wt.eu) wrote: Hi Erik, sorry for the long delay. On Thu, May 12, 2016 at 11:26:29AM +0200, Erik Seres wrote: > If the client provides the server name

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

Hi Erik, sorry for the long delay. On Thu, May 12, 2016 at 11:26:29AM +0200, Erik Seres wrote: > If the client provides the server name it intends to connect to, per RFC3546, > Section 3.1. Server Name Indication, this patch will pass the server name > onto the backend server as part of the

[PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

If the client provides the server name it intends to connect to, per RFC3546, Section 3.1. Server Name Indication, this patch will pass the server name onto the backend server as part of the proxy protocol v2 header. The patch defines the new SSL subtype PP2_TYPE_SSL_SNI and the corresponding