summaryrefslogtreecommitdiffstats
path: root/src/testlib/doc/snippets/code
diff options
context:
space:
mode:
authorTimur Pocheptsov <timur.pocheptsov@qt.io>2020-06-03 12:30:41 +0200
committerTimur Pocheptsov <timur.pocheptsov@qt.io>2020-07-28 15:35:41 +0200
commitc9a702a04d4b90b0a04966d7918f01ddfe9808c1 (patch)
tree64c9628c57dedb615405b5af25faeca92be72d0d /src/testlib/doc/snippets/code
parent964f5757ea00c5fd4a8c617e8df1bfa353c5b225 (diff)
QSslSocket (OpenSSL, Windows) - make sure we ignore stale fetch results
The CA fetcher on Windows works on a separate thread, it can take quite some time to finish its job and if a connection was meanwhile closed (via 'abort', 'close' or 'disconnectFromHost') but the socket is still alive/re-used - we don't want to be fooled by the previous fetch 'finished' signal, only if it's fetching for the same certificate. Change-Id: Ibd0a70000ad10cff10207d37d7b47c38e615d0f1 Reviewed-by: MÃ¥rten Nordheim <marten.nordheim@qt.io>
Diffstat (limited to 'src/testlib/doc/snippets/code')
0 files changed, 0 insertions, 0 deletions