On 2019-07-19 14:05, Christopher Faulet wrote:
Le 19/07/2019 à 09:36, Sander Klein a écrit :
--- HTTP/1.1 200 OK Server: nginx Date: Fri, 19 Jul 2019 07:32:03 GMT Content-Type: application/json; charset=UTF-8 Transfer-Encoding: chunked Vary: Accept-Encoding Vary: Accept-Encoding Cache-Control: private, must-revalidate ETag: "178c3f242b0151fe57e02f6e8817ce3a" Access-Control-Allow-Origin: *Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, PATCH, DELETE,HEAD Length: unspecified [application/json] --- Maybe the 'Length: unspecified' has something to do with it.No, this line is reported by wget because there is no "Content-Length" header.
Heh, doh, sorry about that :-)
So, as I said, I pushed a fix (https://github.com/haproxy/haproxy/commit/03627245). It was backported to 2.0. Could you check if it fixes your issue about 502 errors ?
I just pathed up 2.0.2 and tested it. I still get 502's but a lot less. I'm not sure if this is because I do less request/s or I hit something else. The show errors show:
--- [20/Jul/2019:19:34:45.629] backend cluster1-xx (#11): invalid response frontend cluster1 (#3), server xxx (#1), event #0, src x.x.x.x:52007 buffer starts at 0 (including 0 out), 10809 free, len 5575, wraps at 16336, error at position 0 H1 connection flags 0x00000000, H1 stream flags 0x00004094 H1 msg state MSG_RPVER(10), H1 msg flags 0x00001404 H1 chunk len 0 bytes, H1 body len 0 bytes : --- --- [20/Jul/2019:19:40:32.643] backend cluster1-xx (#11): invalid responsefrontend webservices (#18), server xxx (#2), event #13, src x:x:x:x:x:x:x:x:59724
buffer starts at 0 (including 0 out), 16377 free, len 7, wraps at 16384, error at position 0 H1 connection flags 0x00000000, H1 stream flags 0x00004094 H1 msg state MSG_RPBEFORE(8), H1 msg flags 0x00001404 H1 chunk len 0 bytes, H1 body len 0 bytes : 00000 :10}]}} ---There is of course more with the first one, but I do not want to put that on the mailinglist. It seems like a partial response body. I can send it to you private if you want.
For 504 errors, I have no idea for now.
I'm not sure about these 504's either. I had a couple of reports about these and 1 of our developers had it one time, but I haven't seen it myself or seen any proof about this. But like I said, the logs show nothing. I will keep my eye on this.
Description: OpenPGP digital signature