I noticed that FiddlerCore dlls are not strongly named. Is there any version available which is signed with a strong name?
I tried to sign the assembly, but it seems to be protected.
Hi guys,
Since the performance testing tools have been made available to VS2015 I thought I'd try out the webtest/loadtests and found that fiddler can already export directly to that format. The following article talks about custom plugins you can make for the export process but my version of Fiddler doesn't seem to pick them up.
https://blogs.msdn.microsoft.com/slumley/2007/04/17/writing-fiddler-web-test-plugins/
Can anyone else get this working using the method described? For the examples purposes I took all logic out the plugin and still couldn't get it to display in the list of plugins. It does however lock the file when I open Fiddler? Does this feature still work?
Code below:
Fiddler v4.6.3
using Fiddler.WebTesting;
namespace FiddlerPlugin
{
public class FiddlerPluginTest : IFiddlerWebTestPlugin
{
public void PreWebTestSave(object sender, PreWebTestSaveEventArgs e)
{
//Test
}
}
}
---------------------------
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.
The wait completed due to an abandoned mutex.
Type: System.Threading.AbandonedMutexException
Source: mscorlib
at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
at Fiddler.frmViewer.(String[] ) in c:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Viewer.cs:line 2809
at Fiddler.frmViewer.(String[] ) in c:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Viewer.cs:line 2717
Fiddler v4.6.3.50306 (x64 AMD64) [.NET 4.0.30319.42000 on Microsoft Windows NT 10.0.14393.0]
---------------------------
OK
---------------------------
What's odd is I don't have a c:\JenkinsHome directory.
-Eric
Hi:
I downloaded a few .pcap files from http://malware-traffic-analysis.net.
I noticed that Fiddler would complain about CRC mismatch when decoding some gzip streams, and hence it won't display the decoded stream.
I am not quite sure whether the CRC is really wrong, however, looks like IE would decode regardless (since I have no trouble to replay it).
I attached one here. Session 1, session 3 are complained by Fiddler. (I am using the latest version 4.6.3.50306)
Password "infected"
Hello,
To start, let me say I love Fiddler, and have been using it for many years, as I most of the time develop web sites, and so on.
My concern is that at my new work, they are using a f*** proxy with windows authentication, which make very hard to access internet for applications like maven, nodejs, and so on. I just start Fiddler, use localhost:8888 as proxy, and it automatically authenticate on the proxy, which is marvelous :)
All worked fine using Fiddler with "Automatically Authenticate" for several months, until they change the proxy a month ago, and it no more works, but I can't figure why it does not work anymore.
When I start FIddler, I always get the same error for each requests, maybe someone can help:
10:51:14:0770 Automatic authentication of Session #3 was unsuccessful. System.Exception AuthenticationManager.Authenticate returned null.
à Fiddler.Session.() dans c:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Common\Core\Session.cs:ligne 4263
I haven't seen anything special in the request or response, except a line in the response: "Proxy-Support: Session-Based-Authentication" and the lack of Negotiate, but I'm not sure this is related. And even if Basic seems supported, it does not work, as if it has been disabled on proxy side.
This is really anoying, I'll be happy to help if tests are needed on my side.
Just to have more information, this is the dialog:
> Request 1
GET ...
> Response 1
407
Proxy-Connection: Keep-Alive
Proxy-Authenticate: NTLM
Proxy-Authenticate: Basic realm="McAfee Web Gateway"
Proxy-Support: Session-Based-Authentication
> Request 2
GET
Proxy-Authorization: Negotiate TlRMTVNTUAABAAAAl4...AAAAAAAAAAAGAbEdAAAADw==
> Response 2
407
Proxy-Connection: Keep-Alive
Proxy-Authenticate: NTLM
Proxy-Authenticate: Basic realm="McAfee Web Gateway"
Proxy-Support: Session-Based-Authentication
> Request 3
GET
Proxy-Authorization: NTLM TlRMTVNTUAABAAAAB7IIogMAAwAzAAAACwALACgAAAAGAbEdAAAAD0ZSMDU1NzM2MzZMRVVS
> Response 3
407
Proxy-Authenticate: NTLM TlRMTVNTUAACAAAABgAGA...qXDSAQAAAAA=
Proxy-Support: Session-Based-Authentication
> Request 4
Proxy-Authorization: NTLM TlRMTVNTUAADAAAAGAAYA.longer_than_previous.AAAAAAAAAAAAAAAA==
> Response 4
403 AuthorizedOnly
it's over, error page with proxy error
In previsous successfull dialog with th server, I got :
> Response 1
407
HTTP/1.1 407 Proxy Authentication Required
Proxy-Authenticate: NEGOTIATE
Proxy-Authenticate: NTLM
Proxy-Authenticate: BASIC realm="realm_natto"
> Request 2
Proxy-Authorization: Negotiate TlRMTVNTUA...ADw==
> Response 2
HTTP/1.1 407 Proxy Authentication Required
Proxy-Authenticate: NEGOTIATE TlRMTVNTUAA...AcACABRPHpAqXDSAQAAAAA=
> Request 3
Proxy-Authorization: Negotiate TlRMTVNTUAADAAA...pKUzcq6X
> Response 3
it works, the reponse is good
Regards and thanks to have read all long...
Hello,
I'm trying to add a new option in the Tools menu using ToolsAction. Is there a way to control where my new entry will be displayed -- e.g. can I put it at the bottom of the list or the top of the list?
Thanks,
Gary
P.S. Fiddler is such an AWESOME tool! Thank you, Eric Lawrence and the Fiddler Team!
Hello, after running "mono fiddler.exe" is Fildder suppose to start capturing web requests?
I only see the request to www.fiddler2.com/Update.aspx
Thanks Angela
Build number: v4.6.3.50306
Repro steps:
1. Select one session;
2. Pressing shift button + Replay button;
Expected results:
1. A repeat count window should be popped up;
Actual results:
1. An error window pops up first with uncaught exception as attached screenshot;