Unplanned
Last Updated: 07 Apr 2025 06:19 by ADMIN

I am using the following version

Progress Telerik Fiddler Classic v5.0.20253.3311 for .NET 4.6.2

When capturing WebSocket communication with a URL of "ws://10.133.37.150:9999/", the request line in the Inspectors' Headers view is correct as follows:
"GET ws://10.133.37.150:9999/ HTTP/1.1"

However, the URL column in the left pane says "ws://10.133.37.150:9999/", but the correct value is "/".

Also, the Inspectors' Raw tab says
"GET http://10.133.37.150:9999ws://10.133.37.150:9999/ HTTP/1.1", but the correct value is
"GET ws://10.133.37.150:9999/ HTTP/1.1".

I think this is a bug

 

Unplanned
Last Updated: 07 Apr 2025 06:18 by ADMIN

I am using the following version

Progress Telerik Fiddler Classic v5.0.20253.3311 for .NET 4.6.2

After opening a WebSocket, the communication is captured in which the server returns the messages "WebSocket!Message1!" and "WebSocket!Message2!".

With the first WebSocket, these messages are displayed in the "WebSocket" tab as expected.

However, when the exact same interaction is captured again,
these messages are not displayed in the "WebSocket" tab as they are with the second WebSocket.
Instead, they are displayed as the response body in the "Raw" tab of "Inspectors".

Whether the messages are displayed in the "WebSocket" tab or the "Raw" tab of "Inspectors" is random, and there is no visible pattern.

There seems to be a problem with the process of determining the boundary between the WebSocket opening handshake and the WebSocket message exchange.

 

 

 

Completed
Last Updated: 03 Apr 2025 12:54 by ADMIN
Created by: Eric
Comments: 5
Type: Bug Report
1

I'm pretty disappointed in y'all. 

The January 2025 version of Fiddler introduces a pointless "Security" dialog telling the user about what modules Fiddler is loading. I'm sure you thought that this would improve security, but it won't, because the same level of permission needed to add an extension to Fiddler allows the extension to make this dialog not show (base64 is not encryption).

Worse, the dialog is messed up in high-DPI to the point where it's not readable. https://bsky.app/profile/ericlawrence.com/post/3lh2wvht5oc2k

Worse, the dialog's "Always allow" button doesn't do anything when the user is using `-viewer` mode, because when in Viewer mode preferences don't work.

Worse, it looks like you also broke Transcoder extensions (File > Import); after selecting the importer to use, nothing happens.

Please go back to the way things were before. If you'd like to talk to me about Fiddler's Threat Model, I'm happy to help.

Won't Fix
Last Updated: 03 Apr 2025 05:39 by ADMIN
Created by: Eric
Comments: 3
Type: Bug Report
3

It appears that the latest version of Fiddler breaks Fiddler's public interface. The `Fiddler.WebFormats.JSON` interface no longer appears to be available, breaking extensions and scripts that depend upon it.

 

---------------------------
Failed to import NetLog
---------------------------
Fiddler has encountered an unexpected problem. If you believe this is a bug in Fiddler, please copy this message by hitting CTRL+C, and submit a bug report at http://www.telerik.com/forums/fiddler.

Could not load type 'JSONParseErrors' from assembly 'Fiddler, Version=5.0.20253.3311, Culture=neutral, PublicKeyToken=null'.

Type: System.TypeLoadException
Source: FiddlerImportNetlog
   at FiddlerImportNetlog.NetlogImporter..ctor(StreamReader oSR, List`1 listSessions, EventHandler`1 evtProgressNotifications)

   at FiddlerImportNetlog.NetLogFormatImport.ImportSessions(String sFormat, Dictionary`2 dictOptions, EventHandler`1 evtProgressNotifications)


Fiddler v5.0.20253.3311 (x64 AMD64) [.NET 4.0.30319.42000 on Microsoft Windows NT 10.0.26100.0] 
---------------------------
OK   
---------------------------

Need More Info
Last Updated: 18 Feb 2025 02:11 by Qdwkl

I am trying to use settings Tools -> Win8 Loopback Exemptions -> Exempt All -> Save Changes. But it is giving me some error and saving those changes. Following is the error.

Failed to set IsolationExempt AppContainers; call returned 0x57

I am blocked due to this error and cannot perform tests on my application. Pls help.

Thanks

Unplanned
Last Updated: 23 Aug 2024 05:20 by ADMIN

Fiddler currently does not validate that the Fiddler Trusted Root Certificate is not expired when generating certificates, and it generates certificates that have an expiration that is after the expiration of the root certificate. These certificates will not work because the browser validates the expiration of each certificate in the chain.

Browsers have a poor error message for this case and will imply that the Site's certificate is expired when it's actually the ROOT that expired.

When it loads the root certificate, Fiddler should verify that it is not expired, and if it is, it should trigger the RESET ALL CERTIFICATES flow to help unblock the user from this situation.

It should also be changed such that the root certificate is valid for MUCH longer than the site certificates (e.g. 5 years for the root) so this is less likely to happen.

(If you look in the forums, users are hitting this problem and they are not sure why or how to fix it.)

Unplanned
Last Updated: 22 Aug 2024 19:14 by Eric

If I add a filter to hide something like /teams-modular-packages/ after closing fiddler classic and opening new file filter shows as active but is not working. I need to explicit remove filter and add it again. I would understand that filter wouldn't work accross sessions if filters were removed but they aren't and always showing in bottom left corner. This can be easily reproducible. (in this repro i have imported HAR file, not done a live capture)

 

Completed
Last Updated: 16 Apr 2024 06:45 by ADMIN

Hi Team,

We wanted to use Fiddler Classic and when we send for Security Scanning, its flagged as Malicious. From your end, do you have confirmation like it would be false positive. Attached the screenshot where it was flagged as Malicious.

Thanks.

Completed
Last Updated: 29 Mar 2024 02:49 by Ryuu

For legacy reasons, Fiddler logs the message "HTTPSLint> Warning: ClientHello record was {0} bytes long. Some servers have problems with ClientHello's greater than 255 bytes"

This message should be removed because at this point, effectively ALL clienthellos are over 500 bytes and basically all servers are okay with it.

(This message was only relevant around 2014 or so when longer clienthellos started becoming common)

Completed
Last Updated: 28 Mar 2024 10:43 by ADMIN
Created by: Eric
Comments: 0
Type: Bug Report
0

When sending post data, -d option needs to ensure that the data does not start with an @

https://portswigger.net/research/the-curl-quirk-that-exposed-burp-suite-amp-google-chrome

 

BasicFormats.dll - cURLExport.cs

Completed
Last Updated: 28 Mar 2024 10:42 by ADMIN

As noted in the Fiddler book,

Sessions rerouted from one hostname to another using the Host Remapping tool are rendered with a light blue background in the Web Sessions list. HTTPS Sessions that have been rerouted have the X-IgnoreCertCNMismatch and X-OverrideCertCN Session Flags set to avoid raising “Certificate Name Mismatch” errors.

However, there's a bug. In the HostsFile.cs code, there's are several places that look like:

            if (oS.isTunnel) {

                oS["x-overrideCertCN"] = oS.hostname;
                oS["X-IgnoreCertCNMismatch"] = "HOSTS-Ext";
            }

This usually works for browser traffic going through Fiddler (because the HTTPS handshake is typically conducted on the CONNECT tunnel). However, it doesn't work (and the user is spammed with cert error warnings) if the traffic is sent from Fiddler itself (e.g. via Composer or using the "Reissue requests" context menu item). 

The code should look like this:

            if (oS.isHTTPS || oS.isTunnel) {

                oS["x-overrideCertCN"] = oS.hostname;
                oS["X-IgnoreCertCNMismatch"] = "HOSTS-Ext";

           }

Unplanned
Last Updated: 04 Feb 2024 09:49 by piccolo

Hi,

I’m developing a .NetFramework extension for Fiddler and am finding an issue with clearing bold, italic, strikethrough on the session text in the session list when using “this.session.RefreshUI()”. I’d like to be able to see these changes occur upon a context menu item click, immediately within Fiddler, without having the reload the sessions or the application. I can see the session flags are removed from the session as expected, but the bold, italic, or strikethrough is not unset.

I’m aware there is an option to Mark, Unmark sessions, but this doesn’t fit integrate closely enough with the extension I am developing or do exactly what I would like.

I seem to have no issues with changing the UI-Backcolor or UI-Color and refreshing for the updates to be immediately seen.

I can set UI-Bold, UI-Italic, UI-Strikethrough, but I cannot unset these with RefreshUI().

Is this a bug? Is the RefreshUI() call not doing something for UI-Bold, UI-Italic & UI-Strikethrough which it does do for UI-BackColor and UI-Color?

Thanks,

Jeremy.

Pending Review
Last Updated: 25 Jan 2024 17:38 by Matías

I will be very useful if the font can be configured separately. One font for the composer and results, and the other for the IDE.

If I change the FONT, all the IDE is updated, including the composers, but after RESTARING, the composer has the same font than before

Unplanned
Last Updated: 24 Dec 2023 07:22 by Xriuk
Created by: Xriuk
Comments: 3
Type: Bug Report
1

Related issue: https://github.com/aws/aws-sdk-net/issues/2567

When sending multiple requests to the same domain, sometimes Fiddler alters the headers (in this case by duplicating the user-agent one), and in this case it causes a fail because a precomputed signature of the request does not match.


Need More Info
Last Updated: 24 Dec 2023 03:00 by Eric

good morning 

i got error while capturing my app to auth.btxo.cn

=== Windows 10 64bit OS==

===Protocols I have enabled: <client>;ssl2;ssl3;tls1.0;tls1.1;tls1.2

====== Message from Fiddler v5.0.20211.51073  for .NET v4.6.1
HTTP/1.1 200 Connection Established
FiddlerGateway: Direct
Connection: close

fiddler.network.https> HTTPS handshake to 104.21.46.118 (for #17) failed. System.Security.Authentication.AuthenticationException A call to SSPI failed, see inner exception. < The message received was unexpected or badly formatted

Win32 (SChannel) Native Error Code: 0x80090326

 

Any help ??

Thank you

 

The fiddler response

A SSLv3-compatible ClientHello handshake was found. Fiddler extracted the parameters below.

Version: 3.3 (TLS/1.2)
Random: 65 58 47 1D 28 AB A2 68 50 33 C7 75 1E A4 8B F5 9D A6 FB A0 F9 D2 54 FA 93 D5 AE 78 E5 26 7D 89
"Time": 26/07/1985 15:35:49
SessionID: empty
Extensions: 
server_name auth.btxo.cn
status_request OCSP - Implicit Responder
supported_groups x25519 [0x1d], secp256r1 [0x17], secp384r1 [0x18]
ec_point_formats uncompressed [0x0]
signature_algs rsa_pss_rsae_sha256, rsa_pss_rsae_sha384, rsa_pss_rsae_sha512, rsa_pkcs1_sha256, rsa_pkcs1_sha384, rsa_pkcs1_sha1, ecdsa_secp256r1_sha256, ecdsa_secp384r1_sha384, ecdsa_sha1, dsa_sha1, rsa_pkcs1_sha512, ecdsa_secp521r1_sha512
SessionTicket empty
ALPN http/1.1
extended_master_secret empty
renegotiation_info 00
Ciphers: 
[C02C] TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
[C02B] TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
[C030] TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
[C02F] TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
[009F] TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
[009E] TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
[C024] TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
[C023] TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
[C028] TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
[C027] TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
[C00A] TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
[C009] TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
[C014] TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
[C013] TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
[009D] TLS_RSA_WITH_AES_256_GCM_SHA384
[009C] TLS_RSA_WITH_AES_128_GCM_SHA256
[003D] TLS_RSA_WITH_AES_256_CBC_SHA256
[003C] TLS_RSA_WITH_AES_128_CBC_SHA256
[0035] TLS_RSA_WITH_AES_256_CBC_SHA
[002F] TLS_RSA_WITH_AES_128_CBC_SHA
[000A] SSL_RSA_WITH_3DES_EDE_SHA

Compression: 
[00] NO_COMPRESSION

Need More Info
Last Updated: 01 Nov 2023 15:00 by ADMIN

Help menu to check for updates says:

Error retrieving version information

System.IO.InvalidDataException ... Server Resonse Code = 502
    at [encoding error] ...Updater.cs:Line 90
...

GET /UpdateCheck.aspx?isBeta=False HTTP/1.1 Result 502

Version: 

v5.0.20211.51073 for .NET 4.6.1
Built: Wednesday, December 15, 2021
64-bit AMD64, VM: 84.0mb, WS: 129.0mb
.NET 4.8 WinNT 10.0.19045.0
Won't Fix
Last Updated: 25 Aug 2023 08:14 by ADMIN

Dear Fiddler developers,

 

I was recently inspecting the Punch In and Clock Out system of our company. After I captured the POST to send the punch in packages, I try to replayed it.

The replay functions returened a valid request. It is still valid even if I export the session into curl of a bat fil. But I got a issue after I copy the code into a bigger automatic code. The server I sent report me a 543 error "Please check the shifts." And the map API returned a UTF-8 wrong decode.

 

First I thought that this is because the limitation of both Unix and Windows system, I tried to pipe all the satings into the limitation they desire, 520 as I measured in UNIX. But it did not work.

Later on I watch the debug with the bash -x for about an hour, then I realise that you, the Fiddler program actually somehow turn one % into double %%.

After I replace all the %% with single %, everything works fine.

 

My first doubt is the ChatGPT. But as I was looking through the chat history, the ansewer is no, The problem is somewhere before I ever peate the code to ChatGPT to run. So I regenerated the whole cURL code from Fiddle, and yes this fault is your issue.

 

Please keep me updated if you fix that problems. Also, maybe I am ingnorant on this common problem. I am just a noob in the holy I.T. stuffs.

Yours,

Neil.

Unplanned
Last Updated: 16 Aug 2023 06:36 by ADMIN

Fiddler's update check will always fail by default because you've disabled TLS/1.0 support on your server and Fiddler's now-very-outdated TLS config only enables TLS/1.0 by default. The user must manually go into Tools > Fiddler Options > HTTPS and change the Supported protocols string to <client>;tls1.2 to fix this problem (and to also fix problems with the Composer and any other Fiddler features that do not pass through traffic through a client that supports later TLS.

This is tracked by oAcceptedServerHTTPSProtocols in Config.cs.

Declined
Last Updated: 05 May 2023 07:24 by ADMIN

Fiddler classic uninstall after epic app & valorant online game not working some error as to come valorant error code : val 29

Epic error code : 404

Need More Info
Last Updated: 05 May 2023 07:09 by ADMIN
Created by: Michael
Comments: 1
Type: Bug Report
0

Fiddler would NOT allow me to save the file.  We tried this multiple times to various file locations. 

I do not have Visual Studio installed on my PC -- so I selected the latest verison in this form because it is a REQUIRED field. 

Fiddler provided the text below. 

 

---------------------------

Awww, Fiddlesticks!

---------------------------

Fiddler has encountered an unexpected problem. If you believe this is a bug in Fiddler, please copy this message by hitting CTRL+C, and submit a bug report at http://www.telerik.com/forums/fiddler.

 

Could not find file 'C:\Users\629243897\Documents\IBMSPend on v85 debug - 2 refreshes after logon.saz'.

 

Type: System.IO.FileNotFoundException

Source: mscorlib

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

 

   at System.IO.FileInfo.get_Length()

 

   at Fiddler.frmViewer.actSaveSessionArchive(String , String
, Session[] ) in C:\Jenkins\Fiddler_Windows\workspace\Fiddler2\Fiddler.Shared\Viewer.cs:line 6808

 

 

Fiddler v5.0.20211.51073 (x64 AMD64) [.NET 4.0.30319.42000 on Microsoft Windows NT 10.0.22621.0]

---------------------------

OK   

---------------------------


1 2 3 4 5 6