Date: Thu, 16 Aug 2018 23:36:51 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 230681] benchmarks/httperf: for TLS > 1.0 first request send to server is garbage / random bits Message-ID: <bug-230681-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230681 Bug ID: 230681 Summary: benchmarks/httperf: for TLS > 1.0 first request send to server is garbage / random bits Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: jlaffaye@FreeBSD.org Reporter: szander@netflix.com Flags: maintainer-feedback?(jlaffaye@FreeBSD.org) Assignee: jlaffaye@FreeBSD.org When I use TLS 1.1 or TLS 1.2 the first request that is send to the server = is completely garbage (looks like some random bits from memory rather than a H= TTP request). Subsequent requests to the same server work fine. I'm not sure wh= at precisely the issue is but I noted that core_ssl_connect() is written such = that httperf can interleave other stuff while connecting. With a more "atomic" connect loop the problem is gone on my test machine:=20 while ((ssl_err =3D SSL_connect(s->ssl)) =3D=3D -1) { int reason =3D SSL_get_error(s->ssl, ssl_err); if (reason !=3D SSL_ERROR_WANT_READ && reason !=3D SSL_ERROR_WANT_WRITE) { fprintf(stderr, "%s: failed to connect to SSL server (err=3D%d, reason=3D%d)\n", prog_name, ssl_err, reason); ERR_print_errors_fp(stderr); exit(-1); } } --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230681-7788>