Hello, Bernd--
Fiddler's Timeline tab set to Client Pipe Map mode is the simplest way to visually see which requests were on sent on which reused client connection. To see similar information in the Web Sessions list, your best bet would be to add a column showing the Session Flag named X-ClientPort.
No, there's no guarantee that Fiddler will reuse connections to the server in the same way that the client uses them to send requests. Inside the OnPeekAtResponseHeaders method, you could add code like:
if ((null != oSession.oResponse) && (null != oSession.oResponse.pipeServer)) {
oSession.oResponse.pipeServer.ReusePolicy = PipeReusePolicy.MarriedToClientPipe;
}
This will tag the connection to the server such that it cannot be reused except by a request sent on the connection that originally established it.
Regards,
Eric Lawrence
Telerik
Fiddler's Timeline tab set to Client Pipe Map mode is the simplest way to visually see which requests were on sent on which reused client connection. To see similar information in the Web Sessions list, your best bet would be to add a column showing the Session Flag named X-ClientPort.
No, there's no guarantee that Fiddler will reuse connections to the server in the same way that the client uses them to send requests. Inside the OnPeekAtResponseHeaders method, you could add code like:
if ((null != oSession.oResponse) && (null != oSession.oResponse.pipeServer)) {
oSession.oResponse.pipeServer.ReusePolicy = PipeReusePolicy.MarriedToClientPipe;
}
This will tag the connection to the server such that it cannot be reused except by a request sent on the connection that originally established it.
Regards,
Eric Lawrence
Telerik
See What's Next in App Development. Register for TelerikNEXT.