Can fiddlercore be used for both reverse proxy and regular proxy at the same time?

3 posts, 0 answers
  1. John
    John avatar
    12 posts
    Member since:
    Dec 2012

    Posted 04 Mar 2015 Link to this post

    (posted in the wrong sub folder.)


    Hi all,

    With fiddlercore app installed on the IIS server, I would like to capture both incoming https request as well as outgoing https requests.
    Is this possible?

    will this require 2 separate fiddlercore apps to be running? The main fiddler client application seems to only allow one or the other.



  2. Eric Lawrence
    Admin
    Eric Lawrence avatar
    833 posts

    Posted 05 Mar 2015 Link to this post

    Hello

    Fiddler and FiddlerCore can capture both inbound and outbound traffic if configured appropriately.

    It sounds like you're using FiddlerCore; which version?

    The default program.cs included in the FiddlerCore package shows how to create a new listener for inbound HTTPS connections. You'd update that to use the port and certificate hostname for which you want to act as a reverse proxy for inbound traffic.

    The default listener generated by your Startup() call is what is used to listen to outbound requests. Of course, if you're running in IIS, you need to ensure that the code running in IIS is configured to route its traffic through the FiddlerCore proxy; see e.g. http://www.fiddlerbook.com/fiddler/help/hookup.asp#Q-IIS


    Regards,
    Eric Lawrence
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
  3. John
    John avatar
    12 posts
    Member since:
    Dec 2012

    Posted 05 Mar 2015 in reply to Eric Lawrence Link to this post

    Hi Eric,

    I have a dll extension I wrote that captures the outgoing rest api requests of our asp mvc application. I tried to configure fiddler to intercept incoming api requests, but I couldn't get it to work without doing alterations I didn't like (the url target of the client requester, etc..).  I don't remember the exact details since it was months back.  Also, it wasn't that important back then. But now I need to capture incoming requests too.  Hopefully, the only change I will need is to have iis listen to fiddlercore app and have fiddlercore app listen on 80/443.

    Thanks, I'll look into the example in the book.
Back to Top