Currently, Fiddler Everywhere capture every https traffic. Sometime, decrypt all https traffic are inconvenience and totally make the network broken (eg: Android 7+ devices). Please add this feature of Fiddler Classic.
Thanks!
Colleagues, please add an essential feature of Fiddler Classic called Automatic breakpoints
I'm sure that a bunch of people will migrate to Fiddler Everywhere if you implement this
Thnx
Fiddler for Windows allowed you to add custom columns to Web Sessions list.
Fiddler Everywhere needs this option so I can add in a column to show the IP address of the server being connected to.
Can these methods be added into Fiddler Everywhere:
With Fiddler on Windows an imported HAR file would load into a new window.
Current Fiddler Everywhere appends the HAR file into the current window you have open.
For example, I see my HAR import and it gets appended into the "Live Traffic" session. It should import into a new window like the existing windows version does.
I am trying to login to fiddler anywhere on Ubuntu. But since the system is behind proxy, while logging into proxy, i get network error.
I have configured the proxy in env variables as well as network settings >proxy, but it does not work.
Please provide a way to configure the corporate proxy for fiddler everywhere before login
Hey folks. There is a serious lack of guides/tutorials on using fiddler.
So to set things up you have to use 5 year old stack posts, and if you're lucky things will work.
This has been my biggest issue when it comes to incorporating Fiddler into my workflow.
Right now I'm struggling with setting up a Root CA on Ubuntu (cos the cert is weird).
So yeah. Tl:dr Fiddler Everywhere needs guides and tutorials that are easy to follow and available for multiple OS's
Operating System: macOs Catalina 10.15.4
Step by step instructions on how to reproduce the problem:
You can also do the following to reproduce the problem:
Use case: I work remotely and connect to a VPN. In comparison, Charles Proxy can capture traffic when VPN is on. The comparison was to point out traffic is possible to be captured on VPN to counter any arguments.
Having used the original Fiddles for almost a decade. The new one looks great, but the UI scaling is way too big and spacious for actual production work.
We may have hundreds of requests in one test case and it's important that we see as many requests as possible on one screen so that we can get the whole picture how a service works (for example when reverse engineering something that's badly documented).
With the new UI it's only possible to see few dozen requests, so some kind of UI scaling is required. Also the inspector windows use way too much vertical space. It's really hard to see what's happening in a large request/response.
In my opinion the usability and productivity are more important than how sleek or modern the UI looks. Please prioritize the usability of the UI. Until then, I will be enjoying the classic Fiddler :)
Thanks.
Currently, Fiddler Everywhere just hard-fails on any invalid SSL certificate. More annoyingly, it doesn't explain why the certificate is invalid.
Fiddler Everywhere should:
1. Allow overriding a certificate error (possibly hide this behind an option)
2. Explain what caused a certificate error
I would like to be able to configure the following values via command line in the Mac version of Fiddler Everywhere:
In Preferences:
The best way that I've seen this implemented is in Chrome.
Chrome's settings are by default stored in a JSON file, but a Mac administrator can configure settings using MacOS's built-in preference system (either via the command `defaults write` or using a config profile) which will then enforce the settings.
In the meantime, if there's a text file I can edit, I'd love to do that.
I'm so excited to see you working on a cross-platform version. Your MacOs version was never really usable. Everywhere is already better than the Mac version was!
Edit and resend requests, Compose from scratch and send requests.
I mainly use Fiddler for WebApi testing, debugging, monitoring. The ability to capture, modify, and resend a request is a key feature for me.
Mac/Linux