I have a base64 of a gzip of utf8 bytes of a string - base64(gzip(utg8(string)))
Please add to the TextWizard options in the transform to encode/decode a string to gzip
The .NET Framework has added support for TLS/1.3.
We should do the work to enable TLS/1.3 in Fiddler (it's very little additional work to add "Tls1.3" to the options dialog and the underlying code).
When there's a HAR file with h3 entries, they are either misinterpreted or ignored.
I know how to fix it both in the importer/exporter DLL and in Fiddler.exe.
I can submit a correction.
Hello! The problem is described on this link: stackoverflow
Please add in Filter - feature block named "Request Body" with options "Show only if request body contains", "Hide only if request body contains"
So far Fiddler says it can only import unencrypted sessions from PCAP files.
Various tools and libraries support the SSLKeylogfile environment variable and log the necessary keys.
You can either have them inside the pcapng file or in a seperate file.
It would be nice if Fiddler would accept an optional file with these keys and treated sessions with a suitable key as unencrypted.
This would make things a lot easier in the process.
I use the request LogRequests history to save requests, so that I can replay them when needed. Every month or so when my machine is restarted for an update and if Fiddler is opened, the history is corrupted.
I need a way to either save off certain requests like I can in Postman, etc, or I need Fiddler to have reliable restore points for the history so that the entire history is not corrupted so often.
Please fix or add a feature to address this -
Thanks
HOSTS in fiddler shouldn't change SNI info when Decrypt HTTPS traffic is enabled
When Decrypt HTTPS traffic is enabled and use HOSTS in fiddler, SNI should be keep the same as request, instead of use the one from HOSTS(removed when use IP, or rewrite when use another HOSTS)
When doing an IPR audit what is the actual License Type of Fiddler4 ? eg EULA, MIT Apache etc
https://www.telerik.com/purchase/license-agreement/fiddler-enterprise-support
https://www.telerik.com/download/fiddler
It would be highly useful if there was a "URL splitter" tool added, perhaps as a drop-down entry in the TextWizard, which takes a long-form paramaterized URL and splits it into a line-separated list of individual parameters (and can go the opposite way direction as well).
The "WebForms" subpanel already does this, albeit there's no manual ability to choose what URLs this can be done to ...as far as I'm aware.
I am using Fiddler for 6 months and I found it really nice and simple to understand and get the required information, but one feature in which fiddler is lacking is the NIC information although with fiddler we get the Source and destination IP, port, MIME type, TLS/SSL versions etc but if we get this NIC information it will be complete solution for Web debugging.
Regards,
Faris
Please consider installing a desktop shortcut or start menu shortcut to launch Fiddler viewer (instead of fiddler to listen and capture traffic). This will help folk that want to review fiddler traces from others without launching Fiddler and interfering with locally running apps that misbehave due to Fiddler intercepting traffic by default on launch.
i realize I can create my own shortcut using "fiddler.exe -viewer". But I want to write troubleshooting guides to engineers that are new to both the technology they are learning and Fiddler/HTTP traffic analysis in general. Having two shortcuts created will make it easier to write instructions where we can advise folk to just launch shortcut to viewer to import a session or previously made fiddler saz file from someone else.
Thanks!
For now fiddler just have filter, and it not ignore traffic. Filter just hiding it.
Also Fiddler have option "Capture/Dont capture traffic" via menu File or F12. but it general for all. Also this option NOT work while the target app still use fiddler proxy.
My example problem :
I am using Nox to test MyDownloader app, while apk connect internet or requesting web data its ok to proxified by fiddler. But when I start downloading, the file is downloaded first to Fiddler cache until complete. after complete then fiddler continue request with that file response. That the problem. This also applied to all request in my PC. No problem if size just 20MB. But above 100M, 500MB, 1GB, sometime it make fiddler hang.
Also when i download file, then cancel it, fiddler still download file until complete. So to cancel that in fiddler, i need to disconnect it first.
For now, to bypass my problem i also using Proxi*fi*er filter to selecting mimetype.
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.
我想修改一下Composer的功能,
请问Eric:
1. 在代码里Fiddler有什么方法可以把发送的请求信息记录到Composer History列表?(重点)
2. 点击Excute按钮,是怎么把请求记录下来的?记录的请求保存在什么位置?
期待Eric的答案。
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.
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.
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).
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.
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