On Thu, Dec 05, 2019 at 11:13:00AM +0100, Tim Düsterhus wrote: > Ricardo, > > Am 05.12.19 um 10:28 schrieb Ricardo Fraile: > > Does HAproxy some raw output after the TLS negotiation, logging is > > good, but in some cases, like this, it's hard to know root cause. > > > > You should be able to retrieve the last error by sending `show errors` > on the admin CLI socket. > > Example for your request: > > > [05/Dec/2019:11:11:46.197] frontend fe_http (#1): invalid request > > backend <NONE> (#-1), server <NONE> (#-1), event #0, src 127.0.0.1:49132 > > buffer starts at 0 (including 0 out), 16347 free, > > len 37, wraps at 16384, error at position 22 > > H1 connection flags 0x00000000, H1 stream flags 0x00000012 > > H1 msg state MSG_HDR_NAME(17), H1 msg flags 0x00001410 > > H1 chunk len 0 bytes, H1 body len 0 bytes : > > > > 00000 GET / HTTP/1.1\n > > 00015 Header1 Authorization\n
And here of course the error is the missing colon after "Header1", as spaces are not allowed in header names. Willy
