Impact of capturing https application crash on other applications

4 posts, 1 answers
  1. Alex
    Alex avatar
    2 posts
    Member since:
    Mar 2019

    Posted 28 Mar 2019 Link to this post

    Hi,

     

    I'm interesting to know what will happen to an application (chrome browser, for example), if https capturing application that uses fiddler core, crashes (for reasons not related to fiddler core)? Will chrome continue to work? What about https sessions that chrome had?

     

    Thanks,

    Alex.

  2. Simeon
    Admin
    Simeon avatar
    238 posts

    Posted 28 Mar 2019 Link to this post

    Hi Alex,

    If FiddlerCore stops working, most probably you will get a proxy connection error in the browser. It will continue to work, but it will not be able to connect to the Internet, unless you start FiddlerCore again or fix your Internet proxy settings. If the website/app you open is able to work offline you will be able to continue to use it, otherwise the browser will show you a connectivity error on the first request while FiddlerCore is down.

    Regards,
    Simeon
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. Alex
    Alex avatar
    2 posts
    Member since:
    Mar 2019

    Posted 28 Mar 2019 in reply to Simeon Link to this post

    Thank you for fast answer. I got a follow up question: when fiddler application that used to capture https traffic from a browser stops (not crash, just application exit), a browser seems to be capable to continue to work (i.e. access web content)… What the difference between this scenario and application crash case?

     

    Thanks,

    Alex.

  4. Answer
    Simeon
    Admin
    Simeon avatar
    238 posts

    Posted 28 Mar 2019 Link to this post

    The difference is that FiddlerCore reverts your Internet proxy settings on exit.

    Let me explain.

    On startup FiddlerCore reads your Internet proxy settings and starts to use them as it own proxy settings. Then FiddlerCore changes your Internet proxy settings to 127.0.0.1:8888 (where FiddlerCore proxy runs). This is how FiddlerCore chains to the proxy you use.

    On shutdown FiddlerCore changes your Internet proxy settings to the initial value.

    Of course, this whole process is open for modification. I have just described the default behavior.

    Regards,
    Simeon
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top