I thought it could, but cannot get it to do anything.
We're running Fiddler2 on the WCF 4.5 client side of a Java web service, Windows 7, Soap.
When I turn capturing on and send a request from my client app, I'd like to see what is actually being sent to the service including the Soap envelope and any request headers. My problem is that the headers the service is expecting do not match the headers I'm sending, particularly the Content-Type, but I have no view of the headers so I can't tell what I'm sending.
I do see a file captured, but what's in it is meaningless to me. When I open the Raw tab I see the mish-mash below. Either it tells me what I already know, or nothing at all, but hasn't anything to do with the soap message or headers. If I open the Headers tab it's just more garbage. I can't even tell if it's looking at my client or something else!
I've read that you have to change ports in your web.config, which I've tried - same mish-mash. Any clues???
CONNECT phase2.5010.core.edifecs.com:443 HTTP/1.1
Host: phase2.5010.core.edifecs.com
Proxy-Connection: Keep-Alive
A SSLv3-compatible ClientHello handshake was found. Fiddler extracted the parameters below.
Version: 3.1 (TLS/1.0)
Random: 53 27 58 06 5A B4 31 79 D1 41 6A EC F4 54 A0 BB C3 95 60 4D 54 D7 32 BD 9A F5 75 1C D7 AF DB CD
SessionID: empty
Extensions:
renegotiation_info 00
server_name phase2.5010.core.edifecs.com
elliptic_curves secp256r1 [0x17], secp384r1 [0x18]
ec_point_formats uncompressed [0x0]
Ciphers:
[002F] TLS_RSA_AES_128_SHA
[0035] TLS_RSA_AES_256_SHA
[0005] SSL_RSA_WITH_RC4_128_SHA
[000A] SSL_RSA_WITH_3DES_EDE_SHA
[C013] TLS1_CK_ECDHE_RSA_WITH_AES_128_CBC_SHA
[C014] TLS1_CK_ECDHE_RSA_WITH_AES_256_CBC_SHA
[C009] TLS1_CK_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
[C00A] TLS1_CK_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
[0032] TLS_DHE_DSS_WITH_AES_128_SHA
[0038] TLS_DHE_DSS_WITH_AES_256_SHA
[0013] SSL_DHE_DSS_WITH_3DES_EDE_SHA
[0004] SSL_RSA_WITH_RC4_128_MD5
Compression:
[00] NO_COMPRESSION
We're running Fiddler2 on the WCF 4.5 client side of a Java web service, Windows 7, Soap.
When I turn capturing on and send a request from my client app, I'd like to see what is actually being sent to the service including the Soap envelope and any request headers. My problem is that the headers the service is expecting do not match the headers I'm sending, particularly the Content-Type, but I have no view of the headers so I can't tell what I'm sending.
I do see a file captured, but what's in it is meaningless to me. When I open the Raw tab I see the mish-mash below. Either it tells me what I already know, or nothing at all, but hasn't anything to do with the soap message or headers. If I open the Headers tab it's just more garbage. I can't even tell if it's looking at my client or something else!
I've read that you have to change ports in your web.config, which I've tried - same mish-mash. Any clues???
CONNECT phase2.5010.core.edifecs.com:443 HTTP/1.1
Host: phase2.5010.core.edifecs.com
Proxy-Connection: Keep-Alive
A SSLv3-compatible ClientHello handshake was found. Fiddler extracted the parameters below.
Version: 3.1 (TLS/1.0)
Random: 53 27 58 06 5A B4 31 79 D1 41 6A EC F4 54 A0 BB C3 95 60 4D 54 D7 32 BD 9A F5 75 1C D7 AF DB CD
SessionID: empty
Extensions:
renegotiation_info 00
server_name phase2.5010.core.edifecs.com
elliptic_curves secp256r1 [0x17], secp384r1 [0x18]
ec_point_formats uncompressed [0x0]
Ciphers:
[002F] TLS_RSA_AES_128_SHA
[0035] TLS_RSA_AES_256_SHA
[0005] SSL_RSA_WITH_RC4_128_SHA
[000A] SSL_RSA_WITH_3DES_EDE_SHA
[C013] TLS1_CK_ECDHE_RSA_WITH_AES_128_CBC_SHA
[C014] TLS1_CK_ECDHE_RSA_WITH_AES_256_CBC_SHA
[C009] TLS1_CK_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
[C00A] TLS1_CK_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
[0032] TLS_DHE_DSS_WITH_AES_128_SHA
[0038] TLS_DHE_DSS_WITH_AES_256_SHA
[0013] SSL_DHE_DSS_WITH_3DES_EDE_SHA
[0004] SSL_RSA_WITH_RC4_128_MD5
Compression:
[00] NO_COMPRESSION