It's huge, doesn't have anything to do with Fiddler besides being a Telerik product, and I have no interest in it after having used previous Telerik toolkits. People already deal with ads when consuming content. Don't add them to shit we use when doing work.
Where specifically did you set the filter? If you right-click the Session and choose "Properties", what are the flags on the unexpectedly-visible Session? (By default, Fiddler doesn't hide sessions which resulted in HTTP Protocol Violation errors).
Using the exported wcat file as test automation input, basically read and issue each and every http request from the wcat script, However, the put and delete message was missing
The program is always stuck to death recently and the port 8888 is occupied，change other port can't catch the reqeust。 command netstat -ano|findstr 8888 can't find 8888 is occupied.
There should be an option to limit bandwidth for certain request responses and not all in the way we have Autoresponder implemented. It should match the rule and apply the limit accordingly. So that we can check how a particular API from that domain is only behaving instead of simulating the entire sessions from a particular domain.
Microsoft appears to have moved their web developer documentation from MSDN to MDN, making searches from Fiddler's toolbar return useless results. Please consider making the Search Cue text and Search URL configurable via a preference and set the defaults to "Search MDN" with a URL of https://developer.mozilla.org/en-US/search?q=$SEARCHTERMHERE&topic=apps&topic=html&topic=css&topic=js&topic=api&topic=canvas&topic=svg&topic=webgl&topic=mobile&topic=webdev&topic=http&topic=webext&topic=standards
To be clear, the problem here is that Fiddler updated the certificate they were using to sign the builds without updating the AutoUpdater's code that checks the certificate information. This should have never happened, but certainly should have occurred exactly once-- after you update to a build signed with the new certificate, you should never see this error again.
I'm a software tester. I often use composer to test HTTP requests.But composer needs to fill in the standard head, which is troublesome.Fiddler may enhance composer and add the standard HTTP header selection box. The history module adds some columns, such as name, URL, method, etc.I hope Fiddler is getting stronger and stronger.
I want to search (find) items in the request and response XML views. Currently it is painful. I have to copy the text out from Fiddler and then paste it into another application and do a search there.
We have filter to "Show only Internet Explore traffic" Like wise need filters for other browsers as well
When Fiddler generates a certificate based on the original server certificate (using oSession["X-UseCertCNFromServer"]), it doesn't include all ServerAltNames from the original certificate.
This is current version
Managing Composer history is pretty minimal LIFO. The ability to "rename" is somewhat hidden (right-click > Comment), but after doing so it would be nice to alphabetize it (or manually sort them). I thought about exporting and reimporting, but renumbering the .raz files is tedious.
Fiddler is perhaps the single most versatile piece of software I've ever had the pleasure of working with, and as such it would make life and work easier for countless testers and developers (and those of us combining these jobs). The idea is to be able to sniff packets going through a remote machine—passively. Doing it with wireshark requires me to ssh over into the machine and start tcpdump writing to stdin, from which wireshark then reads: ssh email@example.com "/usr/sbin/tcpdump -i eth0 port 80 and http -s 0 -w -" | "/cygdrive/c/Program Files/Wireshark/Wireshark.exe -k -i -" It starts a wireshark session and lets me see the captured packets in real time, which infinitely more convenient than any mucking about with remote saves with tcpdump, etc. But I don't have access to the convenience of Fiddler UI, and I would kill for it. In fact, even if I save the remote wireshark capture, Fiddler would claim that there is no IPv4 or IPv6 traffic in the pcap-ng (or pcap, or tcpdump...) capture, even though Wireshark clearly shows all the relevant http requests from which to glean the information. My current (and actually nicely working) solution is to use iptables to route all outgoing traffic from port 80 on the remote host to Fiddler's port 8888 in remote capture mode. It has its benefits in that I get full control over the sessions, but it is not always a viable solution, and to be able to passively monitor with Fiddler in real time would give it yet another level of versatility and omnipower! :)
Your software correctly throws up a big yellow warning message about when the system proxy has changed. But after that it seems not to realize when it's changed ....yet again ... back to being "checked" under the Windows "Lan Settings" dialog boxes. So, not a big deal but if you can make the message go away by monitoring that setting it would be cool. Or maybe even change the message to "green" when the checkbox gets ticked again and let the user dismiss it that way just so they know the current state. So, bounce between green and yellow colors depending on the "current live" setting. That would be fun! :) Or just take it away and put back up as the user playfully ticks and unticks the box to see if your software is paying attention. More fun!!!
Related to forum thread: https://www.telerik.com/forums/fiddler-no-longer-capturing-web-service-requests-in-net We found that .NET Core projects use WinHTTP instead of WinINET. As Fiddler registers itself only as a proxy for WinINET, traffic from these projects do not show up in Fiddler. While a manual workaround exits, it would be good if there was at least an option to register Fiddler as a proxy for WinHTTP as well. On a side note: We've seen that even node.js traffic does not show in Fiddler as well. We've not researched the cause as it wasn't critical to us at that time. But, it could also be due to the same reasons.