Hi Tim, Noted for SNI and routing.
User were not able to reproduce the issue when I've re-enable H2. I've kept the header capture active if I'm ever notified of an issue again. -- Ionel GARDAIS Tech'Advantage CIO - IT Team manager ----- Mail original ----- De: "Tim Düsterhus" <[email protected]> À: "Ionel GARDAIS" <[email protected]>, "haproxy" <[email protected]> Envoyé: Mardi 5 Octobre 2021 21:23:58 Objet: [*EXT*] Re: host-based be routing with H2 Ionel, On 10/5/21 3:56 PM, Ionel GARDAIS wrote: > Currently, backend selection is made with > use_backend %[req.hdr(host),lower] > > Would > use_backend %[ssl_fc_sni,lower] # Layer 5 > or > use_backend %[req.ssl_sni,lower] # Layer 6 > help with H2 ? > That would be a big fat NO. SNI is ***never*** the correct solution to perform routing. In fact it will make the situation even worse for you. ------------- req.hdr(host) is the correct solution and I am surprised that it does not work for you. Consider adding 'capture request header Host len 50' to your frontend and then share the log lines for affected requests. With the httplog format they should then indicate both the host as seen by HAProxy as well as the backed/server selected. Best regards Tim Düsterhus -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
