1 write to ConnectCallback
System.Net.Requests (1)
System\Net\HttpWebRequest.cs (1)
1789
handler.
ConnectCallback
= async (context, cancellationToken) =>
9 references to ConnectCallback
System.Net.Http (9)
System\Net\Http\HttpRequestMessage.cs (2)
139
/// <see cref="SocketsHttpHandler.
ConnectCallback
"/>. When a request is sent over multiple connections (for
143
/// <see cref="SocketsHttpHandler.
ConnectCallback
"/>: when the request is served over such a tunnel, the callback
System\Net\Http\SocketsHttpHandler\ConnectionPool\HttpConnectionPool.cs (1)
690
Trace($"{nameof(SocketsHttpHandler.
ConnectCallback
)} completing asynchronously for a synchronous request.");
System\Net\Http\SocketsHttpHandler\HttpConnectionBase.cs (1)
87
/// the same id can be surfaced to <see cref="SocketsHttpHandler.
ConnectCallback
"/> and telemetry.</summary>
System\Net\Http\SocketsHttpHandler\SocketsHttpConnectionEvictionContext.cs (3)
51
/// <see cref="SocketsHttpHandler.
ConnectCallback
"/> returned a stream that is not backed by a socket.
60
/// <see cref="SocketsHttpHandler.
ConnectCallback
"/>. It allows the eviction decision to be correlated
64
/// For an HTTP CONNECT proxy tunnel the id seen by a custom <see cref="SocketsHttpHandler.
ConnectCallback
"/>
System\Net\Http\SocketsHttpHandler\SocketsHttpPlaintextStreamFilterContext.cs (2)
47
/// <see cref="SocketsHttpHandler.
ConnectCallback
"/>, the
55
/// connection's id (the one the <see cref="SocketsHttpHandler.
ConnectCallback
"/> observed), and on the