Connections created for UDS listeners don't generate explicit EV_CLOSED events in libevent. Instead, they signal connection close as EV_READ | EV_WRITE, relying on a failed EV_READ to detect close. This is problematic in pipelined HTTP/1.1 connections, where read has been disabled between requests, since no EV_READ is seen. See
|
read_callbacks_->connection().readDisable(true); |
.
Will disable tests of this condition for now, since the behavior is essentially that we don't support UDS + early connection notifications.
Connections created for UDS listeners don't generate explicit
EV_CLOSEDevents in libevent. Instead, they signal connection close asEV_READ | EV_WRITE, relying on a failedEV_READto detect close. This is problematic in pipelined HTTP/1.1 connections, where read has been disabled between requests, since noEV_READis seen. Seeenvoy/source/common/http/conn_manager_impl.cc
Line 257 in 28cca62
Will disable tests of this condition for now, since the behavior is essentially that we don't support UDS + early connection notifications.