Can't even compose an email correctly.. So:
I experience the same issue however with nginx as a backend. I tried enabling “option httplog” within my frontend, it's rather easy for me to replicate, it affects a few percent of the traffic. I have a site, with a total of 3 requests being performed: - The HTML itself - 1 app.css file - 1 app.js file When checking the console on the browser itself (Firefox in this example), Protocol is empty, remote address is "unknown" and Size is 0 bytes for the app.css file For the app.js file, the protocol is +h2 (where others are seen as HTTP/2.0+h2), the size of the response is 1.93 KB (same as original file) and the content is actually in the response as expected - however, no status code gets returned as well ( https://snaps.hcdn.dk/dWf981KBC0pGZfovP7se.png ) In the haproxy log I see following: Dec 27 20:12:18 localhost haproxy[27270]: 80.61.160.xxx:50011 [27/Dec/2017:20:12:01.692] https_frontend~ https_frontend/<NOSRV> -1/-1/-1/-1/16796 400 0 - - CR-- 1/1/0/0/0 0/0 "<BADREQ>" Dec 27 20:12:18 localhost haproxy[27270]: 80.61.160.xxx:50047 [27/Dec/2017:20:12:18.531] https_frontend~ cdn-backend/mycdn 0/0/0/1/1 200 2242 - - ---- 1/1/0/1/0 0/0 "GET /js/app.js?v=1 HTTP/1.1" So app.css gets the<NOSRV> with a CR-- and a<BADREQ> app.js then again works as it should, however when it arrives at the browser, it doesn't seem to contain all the required information (I'd assume some headers are missing, due to the status code, and remote address is missing). On the backend server itself, it receives the request for app.js, but not app.css I'm not really sure how to make strace generate sane output for haproxy, all I see when stracing processes is something like: \27\3\3@\30\330\330n\341\276\205\240o So won't be able to dig deep into whatever goes on there. Lucas Rolff wrote:
I tried enabling “option httplog” within my frontend, I do have the same issue wit
