Unplanned
Last Updated: 27 Nov 2020 10:06 by ADMIN

When I go to File | Save | All Sessions it defaults to a directory (that is not where I want to store the debug information I collected).  

I store all problems I am working on in a different directory structure.  When I go to SAVE my debug session I would like to set the Default directory (structure) where I save all my other documentation for problems I am working on.  Having to "re-find" my documentation folder multiple times in 20 minutes of saving multiple debug sessions is tedious and non-productive.

I suggest a user preference that has these options:

Set default directory to: ..........   (It will always open to here when a SAVE is done)

Follow Last SAVE directory:  (Check box)     This will open whatever directory location you last did a SAVE to

User Fiddler's Default Location:  (Check box)     This is like a "Reset" to Fiddler's default location.

 

 

Unplanned
Last Updated: 12 Aug 2020 08:36 by ADMIN

Most extensions and inspectors need to access the decompressed/unchunked body bytes to perform their function, requiring them to have an understanding of how to get those decoded bytes. To simplify this, add UnencodedRequestBody and UnencodedResponseBody properties to Session that return a byte[], for example:

            

         public byte[] UnencodedResponse() {
            if (!_HasResponseBody() || !Utilities.HasHeaders(oResponse)) return Utilities.emptyByteArray;

            if (oResponse.headers.ExistsAny(new[] { "Content-Encoding", "Transfer-Encoding" }))
            {
                arrResponse = Utilities.Dupe(mySession.responseBodyBytes);
                Utilities.utilDecodeHTTPBody(mySession.ResponseHeaders, ref arrResponse);
            }
            else
            {
                arrResponse = mySession.responseBodyBytes;
            }
         }

 

GetRequestBodyAsString and GetResponseBodyAsString can then be refactored to call these byte[] properties.

Unplanned
Last Updated: 05 Aug 2020 09:50 by ADMIN
Created by: Eric
Comments: 0
Type: Feature Request
0

Today, if a browser makes a HTTPS request to a site with a certificate error, and the user picks "No" when Fiddler asks whether to accept the Certificate Error, it is very difficult to figure out where the HTTPS request made in error came from.

It would be cool if instead of simply closing the TUNNEL connection, Fiddler instead had an option by which the server connection was rejected but the client connection to the Tunnel got a 200 OK but was connected to a special "DEAD" pipe that returned HTTP/503.

That way, the client could make its HTTP requests to the dead pipe (whose URL and Referer header might reveal from where the request came) allowing the user to debug, but overall security would be maintained (no network connection made insecurely).

Unplanned
Last Updated: 30 Jul 2020 15:41 by ADMIN
Created by: Mihai
Comments: 3
Type: Feature Request
12

Would really appreciate a proper machine based installation again, user-based installs are difficult to manage in corporate/enterprise environments & the psuedo machine install of redirecting install folder & creating new shortcuts isn't great, especially if as you mention yourself extensions wont work.

I understand the advantage of not needing admin rights to install programs, but surely most of the targeted audience for this application would either A) have admin rights, or B) be in a managed environment with deployment software in use (and potentially white-listing/App Control software preventing unauthorized apps to run anyway)

Unplanned
Last Updated: 10 Jun 2020 16:23 by ADMIN
Created by: Carlos
Comments: 5
Type: Feature Request
2
Since most browser's and mobile apps are starting to use HTTP3 it would be nice if Fiddler could also support this.
Unplanned
Last Updated: 01 Jun 2020 07:33 by ADMIN
Created by: Imported User
Comments: 4
Type: Feature Request
1
Currently, the ImageView Inspector is only available for responses.

Why not enable it for requests?
Unplanned
Last Updated: 21 May 2020 14:16 by Eric
Created by: Ronen
Comments: 2
Type: Feature Request
0

Currently Statistics show the time of request:

ACTUAL PERFORMANCE
--------------
ClientConnected: 15:33:43.395
ClientBeginRequest: 15:33:43.725
GotRequestHeaders: 15:33:43.725
ClientDoneRequest: 15:33:43.725

 

It would be useful to know the date of the request as well for projects that span several days.

 

Thank you.

Unplanned
Last Updated: 18 May 2020 11:17 by ADMIN
Created by: Nick
Comments: 1
Type: Feature Request
0

I've been a Fiddler user for longer than I can recall. Recently, whilst setting up a new PC I took the opportunity to try out Fiddler Everywhere. Unfortunately after about 30seconds I had to go back and download the original Fiddler.

Here's just a couple of the things that were show stoppers for me:

- No history for composer - this was a useful addition made to Fiddler that I now can't live without

- No way to copy a request from Inspectors view to Composer

- Switching between Inspector and Composer view resets the Composer screen

- Not able to have Inspector and Composer visible at the same time - this isn't really possible in Fiddler at the moment but it feels like it's easier to switch between inspecting requests and composing requests in Fiddler.

- Enabling Https debugging doesn't trust the certificate

It would be great to have Inspector and Composer either in tabs that can be ripped off into separate windows. Ideally it would be great to have multiple Composer windows

 

Unplanned
Last Updated: 11 Feb 2020 18:24 by ADMIN
Created by: Stephan
Comments: 5
Type: Feature Request
121
HTTP/2 has been a standard since mid-2015.   All major browsers support it,  but adoption is slow because there no good debugging tools.    I want to take advantage of pipelining, server push, etc that comes with HTTP/2 which makes it easier to adopt packages like gRPC.    Having a good debugging story (both capture as well as insertion / modification) would make this more possible
Unplanned
Last Updated: 06 Feb 2020 14:05 by ADMIN
Created by: Ekaterina
Comments: 6
Type: Feature Request
2

Greetings!

For now very popular technology in rest is graphQL

We use it in our project

Could you please add graphQl in Fiddler?

Thx

Unplanned
Last Updated: 09 Dec 2019 10:41 by ADMIN

As it stands today, the "Show only traffic from" combobox in the Filters tab will show the process name, its process ID and its window title, if one is available.

However, command line applications, like dotnet.exe do not show any additional information, which can make it harder to distinguish them when there are multiple instances running.

At that point one needs to open task manager to find the process with the expected command line and figure out its process ID.

 

If the drop down were to show the process full command line, it would eliminate this extra step.

 

Thanks

 

Unplanned
Last Updated: 15 Nov 2019 07:24 by ADMIN
Created by: Jonny
Comments: 1
Type: Feature Request
4

Hi!

Is there any way to disable underlining of URL in Raw Inspector tab? It is very annoying when you try to copy part of the request but in fact open the link in the browser instead.

Unplanned
Last Updated: 14 Nov 2019 15:39 by ADMIN

When right-clicking a session and going into the "Filter Now" context menu, there's a filter option at the bottom which filters by Content-Type. Very useful. However, when using Fiddler's ALT-click function on the session list, ALT-clicking on a particular session's Content-Type column value (in order to select all sessions with that same content-type), it factors in subsequent content-type parameters as a unique content-type.

For example, if back-to-back sessions for a particular website were content-types "application/json" followed by "application/json; charset=utf-8", ALT-clicking on one of their content-type entries in the Content-Type column would not select the other, since ALT-click would view them as different content-types. However, if you right-click either of them and Filter-Now by its content-type (application/json), this will filter both sessions despite the additional parameter appended onto the content-type of the latter session -- this is the more useful methodology, in my opinion.

The Filter-Now rule as it stands is the most/more useful of the two methods, since base content-type is almost always what's most important (in my experience).

Can the ALT-click functionality on Content-Type column values mirror the Filter-Now functionality in only looking at base Content-Type of a session? It would be most useful if so, especially since "charsets" can vary so widely/dynamically across sites, when trying to quickly hone-select on all sessions with application/json (or similar), for example.

Unplanned
Last Updated: 13 Nov 2019 10:57 by ADMIN

For Fiddler to be able to recognize the Edge Chromium process.

To add the Context Menu to Auto replay from the Ribbon Bar where we see the IE Icon and by right click in the request frame to replay it.

 

The first screenshot shows where I would like to see the Edge Chromium listed under.

The second illustration, shows the Context menu Revisit In option.

 

Unplanned
Last Updated: 09 Oct 2019 06:37 by ADMIN

Consider adding System.Core.dll to the default references list. This will allow easier usage of System.Linq in the scripts.

https://groups.google.com/forum/#!topic/httpfiddler/GBmZCOVOcVI

Unplanned
Last Updated: 08 Oct 2019 14:21 by ADMIN
Currently, in Fiddler, when I'm creating a new response in AutoResponder > Create new response... when I choose "Generate file", in order to save created response, by default it is saved on Desktop. Is it possible to add setting in which user can set folder path for generated responses?
Unplanned
Last Updated: 08 Oct 2019 14:20 by ADMIN
Created by: Frank
Comments: 0
Type: Feature Request
1
Would it be possible to update the History section of the Composer so that the urls shown aren't cut off because of the column width? Resizing it is also a chore because first you have to resize the entire section and then the column.
Unplanned
Last Updated: 27 Sep 2019 07:55 by ADMIN
Created by: Imported User
Comments: 4
Type: Feature Request
3
I had request with json body, after exporting to curl, looking at the batch file, i didn't see the body part of the request
Unplanned
Last Updated: 29 Jul 2019 08:56 by ADMIN
Created by: Imported User
Comments: 2
Type: Feature Request
3
When Fiddler generates a certificate based on the original server certificate (using oSession["X-UseCertCNFromServer"]), it doesn't include all ServerAltNames from the original certificate.
Unplanned
Last Updated: 10 Jul 2019 10:38 by ADMIN
WebSockets offer a mechanism for doing compression of messages. Fiddler's WebSocket Inspector should provide a simpler means of viewing such content.

The mechanism looks to be a simple DEFLATE operation: https://tools.ietf.org/html/rfc7692
1 2