> Le 31 août 2019 à 12:29, Willy Tarreau <w...@1wt.eu> a écrit :
> 
> Hi Manu,
> 
> On Thu, Aug 29, 2019 at 03:22:11PM +0200, Emmanuel Hocdet wrote:
>> This patch follows Geoff's patch.
> 
> Thanks for this. I didn't remember we automatically copied the SNI
> into the PP. I'm suspecting that sooner or later we'll need a
> "set-authority" action to complete the set-dst and so-on. We'll see.
> 
> Now merged, thanks,
> Willy
> 
Thanks.

Yes, it’s the next step to set authority, but I wonder what is the right 
approach.
. simply, on server line: proxy-v2-authority <authority> (like it is with sni)
  but I would prefer a more generic way.
. more generic (as you suggest): add a « set-authority » for srv_conn,
  and reused the new « proxy_authority » entry to store it.
 
With « set-authority », in usage we will need a sample fetch « authority » as
« bc_authority » ?
Use case could be « sni bc_authority ».
For PPv2 authority, we will automatically use, in the order: bc_authority, 
fc_pp_authority, ssl_fc_sni.

++
Manu


Reply via email to