Hello, thanks for the explanation.
I have set tracepoints in my code, and can confirm that the server is only actually being hit once, so even if Fiddler is generating three calls, only one is actually being handled. This sounds to me like Fiddler isn't actually calling the service three times, although how you explain the different cookie headers is a mystery.
I only used localhost.fiddler as it was the only way I could see to get Fiddler to show requests made when debugging in Visual Studio. If you have another way, please explain. I'm not sure what you mean by the default system proxy.
It's worth noting that this service call is to get data, so the results will be the same each time it's run, assuming the data wasn't changed between calls of course.
I'm not sure how easy it would be to isolate this issue in a sample project, as this is part of a huge project with hundreds of service calls. This is the only one we've seen that shows this. It was originally reported as a bug by a developer who thought we were making three individual calls instead of one, as Fiddler showed it three times. It was only when I set tracepoints that I found that only one call was actually being made.
Thanks for the reply. Please clarify how to use Fiddler with the default system proxy and I'll try again.