Pending Review
Last Updated: 17 Jun 2019 08:03 by ADMIN
Created by: Tom
Comments: 1
Type: Feature Request
3

Fiddler is great but the composer tab really needs some love. For example, it could do with text manipulation features from other applications - double click selects a chunk of text, but it doesn't appear to be aware of common symbols like : ? # " ' ; etc, instead it highlights up to the next space. If i were to do this in vs code or notepad++ it would be more intelligent about delimiters and highlight the portion before the : or inside the " ".

 

Pressing tab inside the editors moves to the next editor - this seems counter intuitive in this context as you'd expect the editor to insert a tab rather than move you to another field.

 

I've been using fiddler for years and this has always bugged me. I normally edit the request in another application and paste it in, but it'd be great if i could do some basic editing in fiddler itself. It shouldn't be full ide-mode, but a little bit of help would be appreciated.

Simple things that would make this much better:

  • Add a little syntax highlighting/validation (invalid json for example)
  • Autocomplete for known headers
  • Have the url box be expandable, so you can actually edit long requests
  • Intelligent selection based on delimiters or context

 

Cheers

Pending Review
Last Updated: 07 Jun 2019 17:14 by Mason
Created by: Mason
Comments: 6
Type: Feature Request
1
In previous versions, it was possible to see the entire timestamp for a given session timer which would include the date.  In the latest version, it only shows the time (no date) and I can't find any configuration options that would allow a full timestamp.
Pending Review
Last Updated: 27 May 2019 05:49 by Vasilev

Running into more and more issues where the end user are authenticating via a smartcard. If the issue is after the initial handshake then we may be able to turn on Fiddler after the authentication and everything is okay. If the issue is specifically to do with the authentication or authentication screens then we are stuck and have no tool to use to debug the issue, especially when it may involve multiple processes. 

 With appropriate new settings in the Fiddler Options, could the socket connection on a TLS send certificate challenge call the appropriate API to use the SmartCard reader as well as challenge for a pin/biometric instead of reading from a certificate.cer file?  

Under Review
Last Updated: 23 May 2019 21:24 by Hemant
Created by: Imported User
Comments: 4
Type: Feature Request
10
You know,jmx file can be used by jmeter. It's very useful, but fiddler cannot export the response ande request to .jmx.

So regretful.
In Development
Last Updated: 21 May 2019 18:21 by Brandon
Created by: Kostas
Comments: 23
Type: Feature Request
60
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: 21 May 2019 16:24 by Pedro
Created by: Isaac
Comments: 3
Type: Feature Request
14
Lots of development software has dark themes because it is less stress on your eyes and looks cool.
Pending Review
Last Updated: 13 May 2019 15:58 by EricLaw

Hi,

Websocket monitoring is such a cool feature in fiddler. What i´m missing is the possibility to export all messages sent and received via the websocket.

In Wireshark i would associate that functionality with "Follow TCP stream".

 

The reason behind:

I want to search within the websocket communication for certain id´s patterns etc. This is currently not possible as every message is handled separately in fiddler.

What i would expect:

Beeing able to export selected or all messages in the WebSocket pane. (one could think of adding "received","sent" and a timestamp between the messages with a certain beginning to be able to filter those messages later.)

 

I would call the fact that:

- "Save" - "Selected Sessions" "as Text or ZIP" is only saving the websocket HTTP upgrade request together with the response but without the websockets payload

 a bug.

 

Or i am missing something. Comments welcome...

 

Jan

Pending Review
Last Updated: 08 May 2019 15:11 by ADMIN
Created by: Emma
Comments: 1
Type: Feature Request
1
Please add python support to fiddler ,thanks.kepp it sample ,just sample is ok.
Pending Review
Last Updated: 19 Apr 2019 06:37 by Chee Wee
Created by: Chee Wee
Comments: 0
Type: Feature Request
1
Provide ability to autoscroll the WebSocket view when new WebSocket messages are added to the view.
Pending Review
Last Updated: 19 Apr 2019 06:36 by Chee Wee
Created by: Chee Wee
Comments: 0
Type: Feature Request
1
Provide ability to filter out ping/pongs in WebSocket view
Approved
Last Updated: 11 Apr 2019 12:58 by ADMIN

I would like a way to block all transfers made internally by Fiddler unrelated to what is being proxied because it disrupts my tests. I am using Fiddler in test cases where I need the data to be limited to what I'm sending through Fiddler. Every time Fiddler is started it makes one or more connections to fiddler2.com. For example http://fiddler2.com/Banners/BannerVersion.txt and also there's a survey connection sometimes as well. Those requests are redirected most of the time to a cloud server. I have to use various VM images to run some of the tests and I see it a lot in the packet captures. The update check I have blocked in the registry where I set BlockUpdateCheck to True. I could ignore fiddler2.com I suppose. Regardless I don't like it there is SSL traffic I can't account for or decrypt, and even if I could it would still be noise disrupting the data I need to check.

I found a preference fiddler.banners.showdefault and fiddler.telemetry.AskPermission but I'm not sure if they relate.

On a somewhat related point consider an option to disable telemetry, refer to Fiddler Script Editor disable internet access

Approved
Last Updated: 11 Apr 2019 12:45 by ADMIN

My Fiddler log is usually filled with thousands of ClientHello warnings. It's a burden for me to read through the log with all those messages. For example:


23:42:42:4843 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
23:42:42:4863 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
23:42:42:4863 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
23:42:42:4863 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
23:42:42:4983 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
23:42:42:4983 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
23:42:42:5113 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
23:42:42:5123 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance

 

I discussed this with Eric Lawrence in the Fiddler Groups thread HTTPSLint> Warning: ClientHello record was xxx bytes long and he had a few suggestions:

  1. Stop logging these entirely, or maybe log them only when the handshake is between 255 and 512 bytes (https://cs.chromium.org/chromium/src/third_party/boringssl/src/ssl/ssl_test.cc?l=1082&rcl=9f0e7cb314ae64234b928fd379381ae9760a9a5f). I think today the warning in Fiddler is simply >255 bytes. But we should probably get rid of this logging entirely, as the buggy server appliances are probably out of the market at this point. Although maybe show a warning at >767 bytes as a) that's huge, and b) we found that there's a server called Gatling that fails on handshakes that big.
  2. Extend the existing interfaces related to Log handling to allow an extension to "eat" messages so that they don't end up in the log.
  3. Extend the Log tab to make use of that new interface to have an "Ignore regex match" box.

 

Approved
Last Updated: 11 Mar 2019 13:18 by ADMIN
Currently by listening to FiddlerApplication.OnWebSocketMessage it's possible to modify the incoming & outgoing messages but it's not possible to send independent direct messages in or out.

Adding the ability to send direct messages will give more freedom on injecting custom messages in both directions, repeating server response messages etc.
Currently if you need to inject an outgoing message you need to wait for the client to generate a message and only then intercept, modify and forward it. Sometimes the client may wait longer times to respond and a direct message mechanism would be quite useful to generate quicker responses.

From: How to send a new web socket message instead of modifying an existing one?
 (https://groups.google.com/forum/#!topic/httpfiddler/CC5XxiWfpuI) Related to: Add properties to WebSocket object (https://fiddler.ideas.aha.io/ideas/FID-I-146)
Under Review
Last Updated: 20 Feb 2019 23:45 by Roberto
Created by: Imported User
Comments: 1
Type: Feature Request
3
Once I had gotten Fiddler to run (had to tell Mono to run in 32 bit mode) and I had re-created the settings.txt file, I received this error when trying to capture traffic:

Fiddler/FiddlerAttach.applescript:7:87: execution error: /bin/sh: USB,127.0.0.1,8888,on,127.0.0.1,8888,on,0,0,off,0,0,off: command not found (127)
Completed
Last Updated: 19 Feb 2019 11:49 by Ian
Created by: Imported User
Comments: 5
Type: Feature Request
9
My Surface is work on 150% DPI , The App looks unclear.

THX
Pending Review
Last Updated: 13 Feb 2019 21:19 by Eric
Created by: Qiu
Comments: 1
Type: Feature Request
0

Request a lighweight proxy forwarder like combination between Proxifier + AppContainer Loopback Excemption Utility in 1 desktop app. Since Fiddler is too heavy in CPU usage and Proxifier cannot forward any proxy to UWP desktop app (any apps from Windows Store).... no need extra feature but just a proxy forwarder like Proxifier + AppContainer Loopback Excemption Utility that works in any Desktop software environtment like OpenVPN adapter. Thanks.

Pending Review
Last Updated: 13 Feb 2019 21:17 by Eric
Created by: greg
Comments: 1
Type: Feature Request
0

The Tools -> HOSTS is a great feature, especially for situations that prevent local admin rights.  I find it difficult to know that the redirection is functioning when looking at the capture log.  It would be nice if something visual would standout to help draw attention that this rule was applied.

Thank you!

Pending Review
Last Updated: 08 Feb 2019 16:51 by Eric
Created by: Dave
Comments: 5
Type: Feature Request
1

It would be really great to be able to view requests and responses as a formatted json string.  Currently, you can show JSON, which uses some tree format, and you can show raw, which is just a flat hard to use string.

It would also be great to be able to format json inside the request composer so it can be easy to modify.

Pending Review
Last Updated: 01 Feb 2019 16:14 by Eric
Created by: Ashish
Comments: 1
Type: Feature Request
0
I use Fiddler to compose requests in addition to tracing HTTP requests going through my machine. However, Fiddler really lacks in maintaining history of your previously composed requests. In this area, POSTMAN really shines, and therefore, some folks might move to POSTMAN. We don't have to have fancy features but the ability to organize your requests in the History will be much appreciated.
Pending Review
Last Updated: 31 Jan 2019 20:55 by Via

Hi guys. 

I investigate responses from . And Fiddler is tool for this.

But now I need  logs from Fiddler for 2-5 days and compare responses.

Fiddler grabs a lot of memory during 1 day and may cause my PC out of memory.

Request:

Automate autosaving saz files 4 hours with time-date in saz name, clear capture dialog and do it in the loop each next 4 hours.

 

1 2 3 4 5 6