Found the issue on the 10th (I think commit 56b0348).. so yesterday's
commit isn't the (only) problem.. tested with commit 0007d0a the issue also
happens. Reverting only below mentioned commit I can't easily do atm. I'll
check more closely this evening.

Op wo 12 dec. 2018 10:52 schreef Christopher Faulet <
christopher.fau...@capflam.org:

> Le 12/12/2018 à 02:08, PiBa-NL a écrit :
> > Hi List,
> >
> > Didn't have time yet to bisect when it went wrong. But attached testfile
> > produces the following output after 3 curl requests at different speeds,
> > this seems to trigger a problem as the hash of the downloaded content is
> > nolonger the same as it should be, (in my actual environment its a 2MB
> > javascript file that comes from a iis server behind haproxy.). Took
> > already a few hours more than desired to come up with a seemingly
> > reliable reproduction.
> > 1.9-dev10 is the first one i put on my production environment as i think
> > release is imminent so it 'should' be pretty stable ;), (yes i know..i
> > shouldn't assume..) before it was using 1.8.14.. So was quick to revert
> > to that 1.8 again :).
> >
> > Using these settings:
> >
> >       compression algo gzip
> >       compression type text/html text/plain application/json
> > application/javascript
> >       compression offload
> > When these compression settings are disabled, it completes successfully..
> >
> > **** top   2.4 shell_cmd|      exit 1
> > **** top   2.4 shell_cmd|    fi
> > **** top   2.5 shell_out|File1 all OK
> > **** top   2.5 shell_out|File2 not OK 7798551c02a37ce89c77fc18fc415e5b
> > **** top   2.5 shell_out|File3 not OK 3146c4c9fce4da750558bfd9387ffc3b
> > **** top   2.5 shell_status = 0x0001
> > ---- top   2.5 shell_exit not as expected: got 0x0001 wanted 0x0000
> > *    top   2.5 RESETTING after ./PB-TEST/ulticompres/b00005.vtc
> > **   h1    2.5 Reset and free h1 haproxy 51853
> > **   h1    2.5 Wait
> > **   h1    2.5 Stop HAproxy pid=51853
> > **** h1    2.5 STDOUT poll 0x11
> > **** h1    2.5 Kill(2)=0: No error: 0
> > **   h1    2.6 WAIT4 pid=51853 status=0x0002 (user 0.253496 sys 0.000000)
> > *    top   2.6 TEST ./PB-TEST/ulticompres/b00005.vtc FAILED
> > #    top  TEST ./PB-TEST/ulticompres/b00005.vtc FAILED (2.581) exit=2
> >
> > haproxy -v
> > HA-Proxy version 1.9-dev10-3815b22 2018/12/11
> > Copyright 2000-2018 Willy Tarreau <wi...@haproxy.org>
> >
> > Can anyone confirm? Or perhaps even fix ;) Ill try and dig a little more
> > tomorrow evening :).
> >
> Hi Pieter,
>
> There is a bug with the commit 3815b22 when the message is chunked. I
> need to see with Willy how to fix it. BTW, if you revert this commit, it
> should work fine.
>
> Thanks,
> --
> Christopher
>

Reply via email to