Hi,
I got below error when launching fiddler for the 1st time:
"---------------------------
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 load file or assembly 'Xceed.Zip.v5.4, Version=5.4.13572.13590, Culture=neutral, PublicKeyToken=ba83ff368b7563c6' or one of its dependencies. The system cannot find the file specified.
Type: System.IO.FileNotFoundException
Source: Fiddler
at Fiddler.FiddlerApplication.()
at Fiddler.frmViewer.(String[] )
at Fiddler.frmViewer.(String[] )
Fiddler v5.0.20182.28034 (x64 AMD64) [.NET 4.0.30319.42000 on Microsoft Windows NT 6.1.7601 Service Pack 1]
---------------------------
OK
---------------------------
"
Hi Folks,
First of all, love Fiddler, what a great product, and continues to be, on a PC anyway. On Mac, well....., honestly, I don't think you should advertise product when it's still pretty clearly not something you're building a business on. But, I do so hope you get there. And, if it helps, I'd be thrilled to get a fully supported and working Mac product and pay for it.
In any case, I need to add tls1.2 to the Protocol Options list in the "Tools-Options-HTTPs" dialog.
However, trying to click on it, a dialog window opens but it's empty, and flickers constantly until the whole environment crashes with an error message regarding a stack fault. NB: I am starting it as "mono --arch=32 Fiddler.exe".
So, how do I go about getting the options changed there? I've done a whole-harddrive search for a config file somewhere that keeps the options, in the hope I could edit it and start mono Fiddler and that would get it done, but, no luck. So, the window is my only choice at this point and it's simply not working.
Alternatively, perhaps an update to the release that simply includes latest HTTPs protocol options,
Thanks,
KW Landry
Hi.
How i can solve what fiddler does when it captures traffic?
I have a client - server software that stopped working. I have no clue why it stopped and now client gets http 400 bad request.
I installed Fiddler on Win7 PC to capture the traffic for analysis and when i capture traffic the client software works fine. I have disabled almost everythting from options.
HTTPS, Connections, Gateway (no proxy), performance. Nothing enabled from these settings.
Is there anything else that i can disable so i can identify component what affects to client software?
Hello Everyone,
Our organization has a security control in place which disables "WinHTTP Web Proxy Auto-Discovery Service" on the all our Windows 7/8/10 machines. we have started testing Windows 10 release 1803 and with "WinHTTP Web Proxy Auto-Discovery Service" disabled it seems fiddler cannot set the proxy on the machine. This same control is in place for previous Windows 7/8/10 releases as well and I have no issue using Fiddler on these machines.
Did anyone else also encounter a similar issue? Is there an explanation for this problem?
Thank you for your help in advance.
-WindowsGuy
Fiddler on Windows does not allow Mac client's to connect through to https sites when basic auth is enabled in Fiddler. Requests sent to http sites work OK. Also when basic auth is disabled the Mac can connect to both http and https sites without any problems.
It seems that Fiddler does not support the Mac request which includes the http headers:
Fiddler responds with a Connection: close header.
On the Mac this results in a kCFErrorDomainCFNetwork error 310. You can see this most easily in Safari. Note that other applications that do not use the Mac API, such as Chrome work fine.
Testing a proxy server written in C# it seems that the Mac wants the connection to be kept alive and cannot handle Fiddler closing the connection. If the proxy server returns a Connection: keep-alive then the Mac seems to be able to respond with the basic auth credentials.
Question:
Can Fiddler be changed to honour the keep-alive header when denying access with a 407 proxy authentication required?
Setup:
Fiddler v5.0.20182.28034 installed on Windows. Configured to be the system proxy, allow remote computers to connect - enabled, reuse client and server connections - enabled.
Mac High Sierra 10:13.6. Mac network settings configured to use Windows machine with Fiddler as the Web Proxy (HTTP) and Secure Web Proxy (HTTPS)