Hi,
I have been using Fiddler for several years now and one thing has consistently bothered me. Whenever I add a filter, say, "Show only processid X", it will filter out everything else. So far so good. However, if something new comes in (usually visual-studio related) that wasn't on-screen prior to the filter it isn't filtered.
Here are some reproduction steps to see what I mean:
* Open Fiddler.
* Use Composer to write up a post against a local dev API endpoint.
* Wait for other items to show up (via browser, VS, etc.)
* Right-Click the Fiddler post and choose "Show only Process = x"
* Watch everything but that process filter out.
* Wait a few moments.
* In my dev environment, new things keep cropping up.
I have included a screenshot showing that a filter is active, with a new instance of svchost showing up after the filter was applied. Is there some way that I can tell Fiddler to apply my filter to any future traffic in this session and not just previous traffic?
7 Answers, 1 is accepted
Rank 1
Rather unfortunately, I'm unable to reproduce the problem you have. From your screenshot I can see that you have 13 filters. What are the other 12? It could be reproducible only with some combination of filters. Does this happen when this is the only filter applied?
Regards,
Alexander
Progress Telerik
Rank 1
Yes. This happens to me with just a single filter of When Process != x.
Mostly what I see is svchost, wermgr, watson, and Visual Studio (which are my chattiest processes by far) . The strange thing is they keep coming back even with the same PID and me having set it to ignore the service by name and/or PID. Sometimes this happens within a minute, sometimes it takes a few minutes.
Here's a screenshot of me duplicating this just now with a single filter in place.
I've managed to reproduce the problem. The process that succeeded to pass the filters was indeed the svchost and with 408 code, exactly as in your case.
The bug is now added to our backlog. Thank you for reporting it and for going though the process of reproduction with me.
Regards,
Alexander
Progress Telerik
Rank 1
Hi Alexander,
Sorry to hear there's a bug, but I'm glad it's reproducible and fixable! Is there a release note section I could use to see when the fix is released?
Thanks,
Lucas
Rank 1
Just another quick update here.
I've noticed other processes popping up here, but so far they've all had a 408. If I see other result status codes I'll let you know, but for now that seems to be the common element.
Thank you for the follow-up.
Yes, the 408 seems to be the common element here. It would be very nice if you do let me know if any other session with different error code pops out.
Regards,
Alexander
Progress Telerik