1. Rather unfortunately, I was not able to reproduce the problem you have. I started Fiddler with your settings as proxy and used it for days (hundreds of thousands sessions) and the results were not the same. The behavior you experience is not normal, but without actual reproduction we cannot really proceed with fixing it. There is however 1 thing we could try - go ahead and stop "Parse WebSocket messages", restart Fiddler and let it run for the same amount of time. Then you can report back what are the results.
2. You can do that with custom code in FiddlerScript or by building custom extension, but I don't think that this will solve the problem from 1.
3. 4. No, this settings should not affect memory usage.
5. Yes, this seems to be valid example.
6. Yes, just click on "Skip decryption" and it will change to "Perform decryption". The syntax is the same.
7. It highly depends on what strategy the speed test website is using. If it is using plain HTTP and it is sending data through the body of the request then Fiddler's default behavior would cause huge numbers in upload section. In order to fix it we should disable request buffering for given hosts. This can be easily done with FiddlerScript. Just modify the following piece of code and add it to your script file (Rules -> Customize Rules or FiddlerScript tab):
Please, keep in mind that this code snippet is written in C#. If you want to use JScript.NET you may need to change it in order to match its syntax. If you want to use the C# version, please, make sure that the selected scripting language is C# in Tools -> Options -> Scripting.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items