Capture ASP .NET Application Traffic

1 posts, 0 answers
  1. Bill
    Bill avatar
    1 posts
    Member since:
    Aug 2016

    Posted 22 Aug Link to this post

    Greetings,

    I'm banging my head against a wall here and would like to see if anyone here can provide any insight.

    I've added this to my web.config:

    <system.net><br>   <defaultProxy enabled="true"><br>   <proxy proxyaddress="http://127.0.0.1:8888" bypassonlocal="False"/><br>   </defaultProxy><br></system.net>

    I'm capturing non HTTPS traffic. Great.

    All my HTTPS traffic comes through as "Tunnel To", yes, I have "Decrypt SSL" selected and the root certificate trusted.

    I've put this into my protocols: <client>;ssl3;tls1.0;tls1.1;tls1.2

    When I make a call, to get this error in the fiddler logs. "The client and server cannot communicate, because they do not possess a common algorithm for pipe".

    This works outside of Fiddler, so Fiddler is having some sort of issue handshaking.

    I ran a scan on the the first endpoint that errored out on in the logs (It can't handshake with any https endpoint):

     SSLv2      not offered (OK)
     SSLv3      not offered (OK)
     TLS 1      offered
     TLS 1.1    offered
     TLS 1.2    offered (OK)

    I then did some research and added this to my script:

    if (oSession.HTTPMethodIs("CONNECT") && oSession.HostnameIs("dev-wsv-OMITTED.OMITTED.ad"))<br>        { <br>            oSession["x-OverrideSslProtocols"] = "tls1.0";<br>        }

    This had no impact.

    So the $64,000 question is, why can't Fiddler handshake with any endpoints when the server can? Any advice or input would be great!

    Thanks!

Back to Top