I ran in debug mode and found the issue :
0000156e:ft-public.clireq[000c:000d]: PUT
/api/products/5/versions/5/documentations HTTP/1.1
0000156e:ft-public.clihdr[000c:000d]: X-CSRF-TOKEN:
de035ec0-58a3-4668-9e43-e4b36911d2ff
0000156e:ft-public.clihdr[000c:000d]: Content-Type: application/json
0000156e:ft-public.clihdr[000c:000d]: accept: application/json
0000156e:ft-public.clihdr[000c:000d]: Content-Length: 12605
0000156e:ft-public.clihdr[000c:000d]: Host: edc-ci.geomath.fr
0000156e:ft-public.clihdr[000c:000d]: Connection: Keep-Alive
0000156e:ft-public.clihdr[000c:000d]: User-Agent: Apache-HttpClient/4.5.3
(Java/1.8.0_131)
0000156e:ft-public.clihdr[000c:000d]: Cookie:
CSRF-TOKEN=de035ec0-58a3-4668-9e43-e4b36911d2ff;
JSESSIONID=8Xn2-NKJJuaMo-eI6c5PvSTwxNf5BLugv7e7rmes;
remember-me=Y1luT2VGVXZnMHZvRWN6ZkluY3F6Zz09Olh4UmZmM3BpQVJxaVlZUmhWbkI1MlE9PQ
0000156e:ft-public.clihdr[000c:000d]: Accept-Encoding: gzip,deflate
0000156e:bck-traefik.srvrep[000c:000d]: HTTP/1.1 200 OK
0000156e:bck-traefik.srvhdr[000c:000d]: Cache-Control: no-cache, no-store,
max-age=0, must-revalidate
0000156e:bck-traefik.srvhdr[000c:000d]: Content-Type:
application/json;charset=UTF-8
0000156e:bck-traefik.srvhdr[000c:000d]: Date: Thu, 02 Nov 2017 13:47:18 GMT
0000156e:bck-traefik.srvhdr[000c:000d]: Expires: 0
0000156e:bck-traefik.srvhdr[000c:000d]: Pragma: no-cache
0000156e:bck-traefik.srvhdr[000c:000d]: Strict-Transport-Security:
max-age=31536000 ; includeSubDomains
0000156e:bck-traefik.srvhdr[000c:000d]: X-Application-Context:
application:prod,mysql:8081
0000156e:bck-traefik.srvhdr[000c:000d]: X-Content-Type-Options: nosniff
0000156e:bck-traefik.srvhdr[000c:000d]: X-Xss-Protection: 1; mode=block
0000156e:bck-traefik.srvhdr[000c:000d]: Transfer-Encoding: chunked
[WARNING] 305/144718 (21260) : HTTP compression failed: unexpected behavior of
previous filters
Compression was enabled in the default section with :
compression algo gzip
compression type text/css text/html text/javascript
application/javascript text/plain text/xml application/json
By commenting these two lines, it went OK.
However, I still can’t figure out what is causing this behavior : there are
many other calls to the same URL.
Any clues ?
Regards,
mildis
> Le 1 nov. 2017 à 12:37, Mildis <[email protected]> a écrit :
>
> Hi,
>
> I got a request ending in a PD status.
> However, ‘show errors’ does not tell anything about that.
>
> backend server returned 200, haproxy returned 200 to the client.
> The entire request took 202ms and returned 15k of data : 3/0/0/199/202 200
> 15262
>
> Is there a way to diagnose further the PD status ?
> Maybe make haproxy log the reason why it ended in PD ?
>
> Thanks,
> mildis
