network: fix double close event (#236)
network: fix double close event (#236)

It is theoretically possible that we complete the SSL handshake in
the write ready event. In this case, we may raise a connected event
and have the connection closed. We need to handle this case and not
double raise the event.

tschroed/envoy,lizan/envoy,lyft/envoy,lyft/envoy,dnoe/envoy,istio/envoy,jrajahalme/envoy,sebrandon1/envoy,lyft/envoy,lyft/envoy,tdmackey/envoy,istio/envoy,sebrandon1/envoy,envoyproxy/envoy,amalgam8/envoy,envoyproxy/envoy,tschroed/envoy,lizan/envoy,istio/envoy,htuch/envoy,htuch/envoy,dnoe/envoy,jrajahalme/envoy,lizan/envoy,envoyproxy/envoy,craffert0/envoy,sebrandon1/envoy,amalgam8/envoy,envoyproxy/envoy,istio/envoy,timperrett/envoy,envoyproxy/envoy,envoyproxy/envoy,craffert0/envoy,jrajahalme/envoy,envoyproxy/envoy,rlazarus/envoy,envoyproxy/envoy-wasm,lizan/envoy,istio/envoy,amalgam8/envoy,sebrandon1/envoy,fengli79/envoy,amalgam8/envoy,lyft/envoy,tschroed/envoy,htuch/envoy,rlazarus/envoy,envoyproxy/envoy-wasm,envoyproxy/envoy-wasm,envoyproxy/envoy-wasm,envoyproxy/envoy,envoyproxy/envoy,rlazarus/envoy,dnoe/envoy,istio/envoy,eklitzke/envoy,tdmackey/envoy,tdmackey/envoy,sebrandon1/envoy,timperrett/envoy,envoyproxy/envoy,envoyproxy/envoy,eklitzke/envoy,fengli79/envoy,lizan/envoy,eklitzke/envoy,istio/envoy,envoyproxy/envoy-wasm,eklitzke/envoy,eklitzke/envoy,envoyproxy/envoy-wasm,dnoe/envoy,jrajahalme/envoy,lizan/envoy,eklitzke/envoy,dnoe/envoy,craffert0/envoy,craffert0/envoy,timperrett/envoy,tdmackey/envoy,timperrett/envoy,rlazarus/envoy,envoyproxy/envoy,envoyproxy/envoy-wasm,lyft/envoy,jrajahalme/envoy,fengli79/envoy,jrajahalme/envoy,fengli79/envoy