Hi 

I'm trying to process a 30KB WebSocket message, but both

e.oWSM.PayloadAsString(),
e.oWSM.PayloadAsBytes()

are trimmed.

Unfortunately, manipulations with Prefs don't help

FiddlerApplication.Prefs.SetInt32Pref("fiddler.network.sockets.ClientReadBufferSize", 1000000);
FiddlerApplication.Prefs.SetInt32Pref("fiddler.network.sockets.ServerReadBufferSize", 1000000);
FiddlerApplication.Prefs.SetInt32Pref("fiddler.network.sockets.Client_SO_RCVBUF", 1000000);
FiddlerApplication.Prefs.SetInt32Pref("fiddler.network.sockets.Client_SO_SNDBUF", 1000000);
FiddlerApplication.Prefs.SetInt32Pref("fiddler.network.sockets.Server_SO_RCVBUF", 1000000);         FiddlerApplication.Prefs.SetInt32Pref("fiddler.network.sockets.Server_SO_SNDBUF", 1000000);

Hi everyone,

    I have implemented the code seen (in C#) http://fiddler.wikidot.com/fiddlercore-demo.As library,

I used the FiddlerCore4.dll,provided by installing fiddlercoreapisetup.exe;

When I launch the application, I can see an error (NET::ERR_CERT_AUTHORITY_INVALID) on my browser (Chrome);

I have already tried to figure out by adding a certificate (http://fiddler.wikidot.com/fiddlercore-faq) but the error always occurs.

 

Thanks,

 

I installed Firefox 43 (32) on a Win 10 (64) system yesterday.

It said that Fiddler Hook (4.6.1.5?) was not verified for use with the browser.

Today the version of Firefox went to 43.0.1, same issue.

Altering xpinstall-sigantures-required allows to Fiddler to run but isn't comfortable.

Is there anything else that I can do to fix the signing issue?

 

We're trying to get the latest version of Fiddler to work with our Websense Proxies. The Proxies have an endpoint which forces a PAC file for all of the local browsers. Is there a way to configure Fiddler to work with the Websense proxies? 

Hey all,

I have server to server XML based methods which I use to engage the communication between 2 servers. 

I cannot use SoapUI since we are not using WSDL services, hence I would like to simulate server calls and responses by using Fiddler.

Is there a way of doing so? and if there is, could some one please aid me doing so?

Thanks

I upgraded Fiddler to the latest version (v2.6.1.5) and for some reason it is no longer capturing iOS traffic. I have not actually tried this for many months so admittedly the problem may be unrelated to the upgrade.

I have done this many times in the past where I set the HTTP Proxy on my device to the IP of the machine running Fiddler and it instantly captures all the traffic.
I verified all the settings and everything seems fine. In fact, when I visit http://myip:8888 from my device I successfully receive the Fiddler Echo Service. However no traffic is being captured.

My setup is a laptop and iphone both on the same non-corporate wifi network. 

Any ideas?

Thank you

To begin, let me say that this is an intermittent issue, and I'm not 100% sure it is caused by Fiddler.

I have an application that uses the IXMLHTTPRequest2 interface to make requests. I am trying to mock network requests using FiddlerCore.dll in my tests, but every so often I'm seeing the following behavior:

1. I issue several requests, which succeed.
2. I set up my IXMLHTTPRequest2 object and call Send(), which returns S_OK.
3. Nothing happens for 20 seconds.
4. Windows calls my OnError callback with E_FAIL.

I have added a BeforeRequest handler to FiddlerCore that logs every request seen (whether I end up mocking it out or not) and an OnLogString handler that simply passes through the logs to my test logger. The request doesn't show up anywhere. It seems to have disappeared without a trace somewhere between Windows and Fiddler.

I can't find any information about debugging issues with IXMLHTTPRequest2 on MSDN. Do you have any ideas about what may have happened, or where I can look to understand more?

Thanks,
Louis

Firefox 43 has now officially disabled the fiddler hook addon citing it's unsigned in FF addons.

Could not be verified and has been disabled.

If someone can have a look at that I'd be immensely appreciative. because I love fiddler and use it a lot with FF :)

I need it for security testing. My purpose is to check, how the application would behave, if the adversary presents a certificate with a wrong Common Name (CN) and/or SubjectAltName, but signed by a correct CA.

I believe that the application in test uses HostnameVerifier incorrectly and need to prove it.

Hi, I'm trying to capture https traffic from instagram android app. Trusted certificate was installed, and I can see traffic from http (from instagram app) but not https (but I can see https traffic from some sites link google.com when I use android browser).

I am using windows 8x64 and Fiddler4. In Fiddler https requests appears as follows:

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

Version: 3.1 (TLS/1.0)
Random: 56 6D AC E8 26 31 CA CB 00 E2 AC 68 AD 8F 7E E4 80 72 25 78 26 BB EB 59 C5 16 C3 30 E0 C1 53 C9
"Time": 12/09/2093 14:18:14
SessionID: E4 3C 00 00 91 E9 3F 1E 25 FF 6B 00 87 3D 29 39 3D AB 22 6D 1A 6A B7 01 F5 83 D3 04 0B 14 0F 47
Extensions:
    server_name    i.instagram.com
    ec_point_formats    uncompressed [0x0], ansiX962_compressed_prime [0x1], ansiX962_compressed_char2  [0x2]
    elliptic_curves    sect571r1 [0xE], sect571k1 [0xD], secp521r1 [0x19], sect409k1 [0xB], sect409r1 [0xC], secp384r1 [0x18], sect283k1 [0x9], sect283r1 [0xA], secp256k1 [0x16], secp256r1 [0x17], sect239k1 [0x8], sect233k1 [0x6], sect233r1 [0x7], secp224k1 [0x14], secp224r1 [0x15], sect193r1 [0x4], sect193r2 [0x5], secp192k1 [0x12], secp192r1 [0x13], sect163k1 [0x1], sect163r1 [0x2], sect163r2 [0x3], secp160k1 [0xF], secp160r1 [0x10], secp160r2 [0x11]
    SessionTicket    empty
Ciphers:
    [0004]    SSL_RSA_WITH_RC4_128_MD5
    [0005]    SSL_RSA_WITH_RC4_128_SHA
    [002F]    TLS_RSA_AES_128_SHA
    [0035]    TLS_RSA_AES_256_SHA
    [C002]    TLS_ECDH_ECDSA_WITH_RC4_128_SHA
    [C004]    TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
    [C005]    TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
    [C00C]    TLS_ECDH_RSA_WITH_RC4_128_SHA
    [C00E]    TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
    [C00F]    TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
    [C007]    TLS_ECDHE_ECDSA_WITH_RC4_128_SHA
    [C009]    TLS1_CK_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
    [C00A]    TLS1_CK_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
    [C011]    TLS_ECDHE_RSA_WITH_RC4_128_SHA
    [C013]    TLS1_CK_ECDHE_RSA_WITH_AES_128_CBC_SHA
    [C014]    TLS1_CK_ECDHE_RSA_WITH_AES_256_CBC_SHA
    [0033]    TLS_DHE_RSA_WITH_AES_128_SHA
    [0039]    TLS_DHE_RSA_WITH_AES_256_SHA
    [0032]    TLS_DHE_DSS_WITH_AES_128_SHA
    [0038]    TLS_DHE_DSS_WITH_AES_256_SHA
    [000A]    SSL_RSA_WITH_3DES_EDE_SHA
    [C003]    TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
    [C00D]    TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
    [C008]    TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
    [C012]    TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
    [0016]    SSL_DHE_RSA_WITH_3DES_EDE_SHA
    [0013]    SSL_DHE_DSS_WITH_3DES_EDE_SHA
    [0009]    SSL_RSA_WITH_DES_SHA
    [0015]    SSL_DHE_RSA_WITH_DES_SHA
    [0012]    SSL_DHE_DSS_WITH_DES_SHA
    [0003]    SSL_RSA_EXPORT_WITH_RC4_40_MD5
    [0008]    SSL_RSA_EXPORT_WITH_DES40_SHA
    [0014]    SSL_DHE_RSA_EXPORT_WITH_DES40_SHA
    [0011]    SSL_DHE_DSS_EXPORT_WITH_DES40_SHA
    [00FF]    TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Compression:
    [00]    NO_COMPRESSION

 

Response:

Encrypted HTTPS traffic flows through this CONNECT tunnel. HTTPS Decryption is enabled in Fiddler, so decrypted sessions running in this tunnel will be shown in the Web Sessions list.

Secure Protocol: Tls12
Cipher: Aes128 128bits
Hash Algorithm: Sha1 160bits
Key Exchange: ECDHE_RSA (0xae06) 256bits

== Server Certificate ==========
[Subject]
  CN=*.instagram.com, O=Instagram LLC, L=Menlo Park, S=CA, C=US

[Issuer]
  CN=DigiCert High Assurance CA-3, OU=www.digicert.com, O=DigiCert Inc, C=US

[Serial Number]
  09D816F9BD53DA75B97D26B82B2B5359

[Not Before]
  13/04/2015 21:00:00

[Not After]
  31/12/2015 10:00:00

[Thumbprint]
  18E23BD23F1F5E10FF974BD639F0B1731527AC18

 

Some idea? 

Thanks