Le 19/07/2019 à 09:36, Sander Klein a écrit :
The show errors:

Total events captured on [19/Jul/2019:08:34:25.093] : 31

[19/Jul/2019:08:34:23.405] backend cluster1-xx (#11): invalid response
    frontend webservices (#18), server xxx (#2), event #30, src
    buffer starts at 0 (including 0 out), 16268 free,
    len 116, 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 :

    00070+ :0},"facets":[],"activeFacets":[]},"media":[]}

Thanks. So the problem seems to be the same than the issue #176 on github (https://github.com/haproxy/haproxy/issues/176). I pushed a fix.


I also did this request with wget to see what the response should be,
and it seems that this is the first part of the 297229 bytes long body.
The response headers are:

    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,
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.

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 ?

For 504 errors, I have no idea for now.

Christopher Faulet

Reply via email to