Re: [PR] proto_tcp.c: fix printing of muliple setsockopt errors
Hi Björn, On Mon, Oct 04, 2021 at 04:22:32PM +0200, Björn Jacke wrote: > Hi Willy, > > I lost track of this issue but I caught this up finally again. > > I updated the setsockopt error patch as part of the mptcp branch here: > > https://gitlab.com/bjacke/haproxy/-/commits/bjacke-mptcp Thanks for this. I haven't yet had time to look into it but at least wanted to ack receipt of your message :-) I should have some time this week. Thanks! Willy
Re: host-based be routing with H2
Jarno, On 10/5/21 5:19 PM, Jarno Huuskonen wrote: Have you looked at this thread: https://www.mail-archive.com/haproxy@formilux.org/msg40652.html your issue sounds similar. Is one backend the default_backend (where HTTP/2 requests go) ? Does it work with something like: use_backend %[req.hdr(host),lower,regsub(:\d+$,,)] or use_backend %[req.hdr(host),lower,word(1,:)] That issue with the port being part of the host header for Firefox Websockets should already be fixed in HAProxy 2.4.4. Best regards Tim Düsterhus
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
Re: host-based be routing with H2
Hi, On Tue, 2021-10-05 at 15:56 +0200, Ionel GARDAIS wrote: > Hi, > > I'm having trouble with backend-routing based on host header when H2 is > enabled. > Frontend is https only and all backends are HTTP1. > We're using v2.4.4. > > When the user browser is directed to app2.example.com, it switches to > app1.example.com. > There is one public IP address, certificate is wildcard for the domain, so > app1 and app2 share the same IP and certificate. > When H2 is disabled, all is working fine. > > Currently, backend selection is made with > use_backend %[req.hdr(host),lower] > Have you looked at this thread: https://www.mail-archive.com/haproxy@formilux.org/msg40652.html your issue sounds similar. Is one backend the default_backend (where HTTP/2 requests go) ? Does it work with something like: use_backend %[req.hdr(host),lower,regsub(:\d+$,,)] or use_backend %[req.hdr(host),lower,word(1,:)] (https://www.haproxy.com/blog/how-to-map-domain-names-to-backend-server-pools-with-haproxy/) or using maps: https://www.haproxy.com/blog/how-to-map-domain-names-to-backend-server-pools-with-haproxy/ (use_backend %[req.hdr(host),lower,map_dom(/etc/haproxy/maps/hosts.map,be_default)]) -Jarno > Would > use_backend %[ssl_fc_sni,lower] # Layer 5 > or > use_backend %[req.ssl_sni,lower] # Layer 6 > help with H2 ? > > Thanks, > Ionel > > -- Jarno Huuskonen
host-based be routing with H2
Hi, I'm having trouble with backend-routing based on host header when H2 is enabled. Frontend is https only and all backends are HTTP1. We're using v2.4.4. When the user browser is directed to app2.example.com, it switches to app1.example.com. There is one public IP address, certificate is wildcard for the domain, so app1 and app2 share the same IP and certificate. When H2 is disabled, all is working fine. 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 ? Thanks, Ionel -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
Your DHL Express Shipment Request Confirmation
To: haproxyYour shipment is ready for delivery.Kindly view the attached file to view shipment details and confirm consignee address correct for express delivery.If you have any issues or questions, please do not hesitate to contact our customer service team for assistance.Thank you for shipping with DHL Express! DHL Express Delivery The Mail & Logistics Group. 2021 © All rights reserved.Title: DHL International & Worldwide Image 01 DHL International® Image 02 Image 03 Image 04 DHL International Worldwide® Image 05 Image 06 DHL International Worldwide® Continue With Valid Email And Password To View & Complete Tracking Details Continue
