Currently the composer window allows you to edit the cookies only as a header, that can turn into a nightmare when all of the cookies accumulate to the length of 500-1000 chars and you're trying to edit a single cookie.
The editing box shows only about 70 chars, so navigating to that single cookie you want to edit/delete is nearly impossible.
If you could add a dedicated tab for cookies, like in the inspectors window, that would be very helpful.
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
Simple as that: fiddler everywhere does not capture traffic to localhost, 220.127.116.11 AND when you insert your local address, it captures your request only to return that "
[Fiddler] DNS Lookup for "www.192.168.0.18" failed. System.Net.Internals.SocketExceptionFactory+ExtendedSocketException Device not configured
MAC OSX, using safari.
Other address are captured as expected
I'm running on an Ubuntu 18.04 server. using VNC via gdm3 (gnome) display manager.
The first time I tried to run progress-telerik-fiddler.AppImage, it brought up a dialog asking if I wanted to integrate with VNC and install a desktop icon, to which I answered yes.
The window then closed, and each time I try to run progress-telerik-fiddler.AppImage again, nothing at all happens, as follows:
wxr-xr-x 1 root root 113958410 Mar 25 14:15 progress-telerik-fiddler.AppImage
There is no desktop icon, log, or anything.
tazik@mx-linux:/mnt/Software/Linux $ ./progress-telerik-fiddler.AppImage --no-sandbox License accepted zenity, kdialog, Xdialog missing. Skipping /tmp/.mount_progrekwdZmY/AppRun. 14:44:47.550 › [Product information] Progress Telerik Fiddler 0.5.0 14:44:47.561 › [System information] Linux mx-linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux 14:44:47.698 › Initializing splash screen. 14:44:47.832 › Attempting to run server - 5 attempts left. 14:44:47.832 › Generating random port. 14:44:47.833 › Trying to start server at port . 14:44:49.324 › Fetching .NET Core server status. 14:44:49.338 › Error occurred while fetching .NET Core server  status. Error message: connect ECONNREFUSED 127.0.0.1:39169 14:44:49.338 › Attempting to run server - 4 attempts left. 14:44:49.338 › Generating random port. 14:44:49.338 › Trying to start server at port . 14:44:50.065 › Fetching .NET Core server status. 14:44:50.071 › Error occurred while fetching .NET Core server  status. Error message: connect ECONNREFUSED 127.0.0.1:14105 14:44:50.072 › Attempting to run server - 3 attempts left. 14:44:50.072 › Generating random port. 14:44:50.072 › Trying to start server at port . 14:44:50.788 › Fetching .NET Core server status. 14:44:50.792 › Error occurred while fetching .NET Core server  status. Error message: connect ECONNREFUSED 127.0.0.1:64355 14:44:50.792 › Attempting to run server - 2 attempts left. 14:44:50.792 › Generating random port. 14:44:50.792 › Trying to start server at port . 14:44:51.504 › Fetching .NET Core server status. 14:44:51.509 › Error occurred while fetching .NET Core server  status. Error message: connect ECONNREFUSED 127.0.0.1:4034 14:44:51.509 › Attempting to run server - 1 attempts left. 14:44:51.510 › Generating random port. 14:44:51.510 › Trying to start server at port . 14:44:52.228 › Fetching .NET Core server status. 14:44:52.233 › Error occurred while fetching .NET Core server  status. Error message: connect ECONNREFUSED 127.0.0.1:28542 14:44:52.233 › Attempting to run server - 0 attempts left. 14:44:52.234 › Maximum number of attempts reached - quitting application. 14:44:52.260 › Generating random port. 14:44:52.261 › Trying to start server at port . tazik@mx-linux:/mnt/Software/Linux
I tried to start app but every time nothing happens except short appearing a splash screen. Bellow detail from terminal:
|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
Im using MacOS Sierra 10.12.5
2 BIG Issues are present.
First of all, I don't have an INTERNET connection any more after closing FIDDLER it has to be always running!
Second issue Fiddler is working properly ONLY on the first Start. If closing it and opening it again it's not working at all.
FIX this ASAP
very very critical
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.