I've broken this out from #1593454 as separate feature request ticket.
As a side note, the preconfigured browser instance (the "Open Browser" functionality) can't be started with a specific profile. You can specify a path to a different Chromium browser, but it will always be started with a temporary profile.
The preconfigured browser instance is a great feature, but I don't use it because the launched browser instance does not use my "Default" profile (with extensions, bookmarks, etc). It is possible to launch Chrome from the command line with arguments, including specifying the profile to use.
Would it be possible to include in the Fiddler Browser settings panel a field that allows users to specify arguments to be used when launching the preconfigured browser instance? Or if not then possibly just the profile name to be used?
Why are there not Fiddler everywhere package here?
That might be a deal breaker for many setups that wants to automate as much as possible, I do get Fiddler classic from here and that is great!
We are planning to use Fiddle Everywhere for testing our application, and I downloaded it for test drive. It has lots of functionality, but I couldn't find the specific futures such as Throttle settings(Bandwidth(download and upload), latency, MTU, reliability, stability etc). That is very important to us. So, we need it for our testings.
Any advice, please?
Requested through https://community.getfiddler.com/support/discussions/topics/12000026780
Originally reported here: https://community.getfiddler.com/support/discussions/topics/12000026504
Requested originally from https://community.getfiddler.com/support/discussions/topics/12000025520
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.
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
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.
I am testing an api that uses basic auth. I am trying to use the composer to hit the API. The existing suggestion is to build the authorization header by hand, but I would suggest that the URL field should be able to handle any URL that a browser or CURL can handle, and so I think it should be able to handle basic auth syntax in the URL, for example:
Currently it takes the user and password and separators and sends the whole thing to DNS ("myUser:p@firstname.lastname@example.org"). Even if it ignores the username and password (and why would you) it should parse them out before sending the hostname to DNS. I would be OK with it building the authorization header and removing it from the URL, but I would rather it handle that behind the scenes and leave the URL the way I pasted it in.
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:
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