I'm not 100% sure if this is a bug or it's a feature (of lack thereof) but it goes like this:
On regular fiddler, a great thing to do is to simply copy a raw request to the raw composer, change a param and re-issue it... Fiddler everywhere does not allow that! I have to write headers on a tab and the body on another and yet, there's a "Raw" tab.
The Raw tab unfortunately is not editable (read-only)... I believe that it should be editable
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 :)
I would like to be able to configure the following values via command line in the Mac version of Fiddler Everywhere:
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.
Include a profile concept to enable us to login with our Telerik account and synchronize my settings on all my machines.
Would synchronize all settings, including custom rules, fiddler scripts, filters, AutoResponders and so on.
Filtering traffic as in older Fiddler version for Windows in Fidder-Everywhere for Mac based OS systems.
This is a well required feature for working with fiddler
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
Currently when you want to restart the fiddler session you have to quit and re-enter the program as much as I saw.
It would be better to have a "clear" button to erase everything in the current session, so it's easier to manage sessions.
|1||Ability to execute POST, PUT, GET, DELETE, etc. requests||Highest|
|2||Ability to capture and inspect the response from the server||Highest|
|3||Ability to add body to the request (when applicable)||Highest|
|4||Ability to view/edit the raw CURL syntax||Highest|
|5||Ability to add headers to the request||High|
|6||Different body format (RAW, Json, etc.)||Medium|
|7||Ability to include query parameters||Medium|
|8||History of executed requests||Medium|
|9||Ability to verify the response||Medium|
|11||Multiple tabs for different requests (preserve the state)||Low|
|12||Ability to execute custom script||Low|