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
|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|
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
In Fiddler (and in applications such as Wireshark) it's easy to collapse / switch between different protocols, headers and such.
In the Fiddler everywhere version - you get the entire request/response as a single text block.
It would be great to switch between protocols / collapse the parts you care less about and in general have better controls.
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.
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.
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 :)