I am running HaProxy 1.8 within docker container using a fork of the official build and pointed them to the latest 1.8.0 instead of rc-4. So it is built using openssl1.1
Docker hub link: https://hub.docker.com/_/haproxy/ See the Dockerfile https://github.com/docker-library/haproxy/blob/0c9c27713bfca8505331e0da2664a9454755c7b9/1.8-rc/alpine/Dockerfile Just replaced these two lines ENV HAPROXY_VERSION 1.8.0 ENV HAPROXY_MD5 6ccea4619b7183fbcc8c98bae1f9823d On Sun, Nov 26, 2017 at 11:29 PM Willy Tarreau <[email protected]> wrote: > On Mon, Nov 27, 2017 at 06:15:48AM +0100, Willy Tarreau wrote: > > On Mon, Nov 27, 2017 at 05:10:16AM +0000, Robin Anil wrote: > > > A very stripped down version of config > > > > Thank you, I'll check if anything there can explain this. > > So with your config I'm getting this : > > Finished in 52.3802 seconds > 145 tests, 110 passed, 4 skipped, 31 failed > > I had to disable ssl-mode-async as my openssl version doesn't support it. > > Of the 31, I'm seeing real bugs compared to what is expected to work, such > as : > > 3.8. GOAWAY > Ã 1: Sends a GOAWAY frame > -> The endpoint MUST accept GOAWAY frame. > Expected: Connection closed > Actual: Timeout > > Others are expected for now : > > 3.10. CONTINUATION > Ã 1: Sends a CONTINUATION frame > -> The endpoint MUST accept CONTINUATION frame. > Expected: HEADERS Frame (stream_id:1) > Actual: Connection closed > > 4. HTTP Message Exchanges > Ã 4: Sends a POST request with trailers > -> The endpoint MUST respond to the request. > Expected: HEADERS Frame (stream_id:1) > Actual: Connection closed > > And the other ones are very useful as they likely indicate missing checks. > So I'll take a look. Thanks! > > Willy >
