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.

 

 

Won't Fix
Last Updated: 06 Nov 2020 17:51 by Eric

我想修改一下Composer的功能,

请问Eric:

1. 在代码里Fiddler有什么方法可以把发送的请求信息记录到Composer History列表?(重点

2. 点击Excute按钮,是怎么把请求记录下来的?记录的请求保存在什么位置?

期待Eric的答案。

Won't Fix
Last Updated: 08 Oct 2020 17:09 by Jason

Please consider refraining from (or at least making optional) the sorting of the JSON property keys when using the JSON tree viewer.  For code which sends out complex payloads, having the properties reordered makes it hard to compare the tree to the actual payload sent.  For example, we send startXXX and endXXX properties at the end of our payload, and when Fiddler moves "endXXX" to the top of the tree, debugging becomes a pain.  Please allow the payload to be tree-visualized as constructed.

Completed
Last Updated: 05 Oct 2020 05:18 by ADMIN
Created by: Kostas
Comments: 26
Type: Feature Request
63
I find myself applying the same filters again and again on each launch of Fiddler (I mean the filters listed below the list of requests).

I think it would be really great if you could allow the restoration of previously applied filters (e.g. by having a save/load filters option).

Also, allowing to filter out by "Request Method" would be great too.

Congratulations on this tool, by the way.

It is really great. :)
Under Review
Last Updated: 01 Sep 2020 09:53 by ADMIN
Created by: Isaac
Comments: 6
Type: Feature Request
23
Lots of development software has dark themes because it is less stress on your eyes and looks cool.
Planned
Last Updated: 20 Aug 2020 19:09 by ADMIN
This seems to happen a non-trivial number of times, and it causes clients and scenarios to fail in surprising ways.
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).

Declined
Last Updated: 03 Aug 2020 21:12 by no
Created by: Imported User
Comments: 4
Type: Feature Request
1
Im using windows 7 32-bit both on my desktop and laptop both of them have fiddler 4.6 and both of them doesnt have winconfig. Its supposed to be on the upper left corner , but mines missing on two computer.any idea? can it be activated?
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)

Declined
Last Updated: 14 Jul 2020 20:27 by ADMIN
Not sure if this is a recent change, but I use Microsoft Outlook and Skype, and both are having connectivity issues when Fiddler is running. Also Windows 10 apps seem to be unable to have an internet connection as well.
Under Review
Last Updated: 19 Jun 2020 14:46 by Matthew
Created by: Imported User
Comments: 8
Type: Feature Request
9
Like the JSON and XML tabs, there should be a Protobuf tab that offers to decode protobuf requests and responses.
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

 

Pending Review
Last Updated: 17 May 2020 13:01 by A
May I suggest to publish an interface assembly with Fiddler, containing only the interfaces of all the Fiddler public types?

This way, IntelliSense could be used, both, with ScriptEditor and with any of the Visual Studio products.

That would require Telerik to derive their public classes, like Session, from an interface, like ISession. That interface would need to be stored in a separate assembly that would be published then along with Fiddler.
Declined
Last Updated: 14 May 2020 18:29 by ADMIN
Created by: S
Comments: 3
Type: Feature Request
1
The Spacebar keyboard shortcut only works if you're still focused inside of the session list. If you've clicked anywhere outside of the session list pane, pressing spacebar won't get passed to the session list.

For example, if you've clicked into the inspectors pane, spacebar will get sent to that pane, not the session list. To get back into the session pane (where spacebar would work), you have to either click back inside the session pane, which would change the session selection you were on, or employ some roundabout shift-tab trickery, like clicking the furthest left tab closest to the session list, then shift-tabbing a handful of times to get back into the session list. But this is pretty kludgy.

It'd be great if there was either a keyboard shortcut to switch focus back into the session list, or at least a tabbing shortcut multiplier which switches between panes, e.g., if Ctrl-Tab switches tabs, Ctrl-Alt-Tab switches between panes -- though this particular combo wouldn't work, as it's already claimed by Windows OS.
Under Review
Last Updated: 07 May 2020 07:50 by ADMIN
Sometimes,I need to know response json node's count,but I can only paste it into the json editor to see the quantity.

Please check the pictures in the attachment.
Completed
Last Updated: 29 Apr 2020 13:17 by ADMIN

https://twitter.com/ericlaw/status/1232024946030862336

Today, Fiddler's AutoResponder only automatically replies to a HTTPS CONNECT with a HTTP/200 OK if the capture contains such a response, or if the "Unmatched requests passthrough" box is unchecked. Otherwise, the CONNECT request will pass or fail based on whether the real server is reachable.

This is confusing, and almost never what the user really wants to have happen.

We should add a new checkbox to the AutoResponder titled "Accept all CONNECTs" that when checked, sets a hidden rule equivalent to this rule which can be created manually

    method:CONNECT
    *ReplyWithTunnel

Otherwise, users will be sad when AutoResponder doesn't do what they hope, and they'll wonder why they are getting ERR_TUNNEL_CONNECTION_FAILED error messages in their browser when they have AutoResponder rules for HTTPS requests that they expect to fire.

 

1 2 3 4 5 6