Fiddler as a service

6 posts, 0 answers
  1. Gus
    Gus avatar
    3 posts
    Member since:
    Nov 2014

    Posted 05 Nov 2014 Link to this post

    Hi
    i have followed the guide to run Fiddler as a service and it works OK. However my customrules.js is not being used.
    I have added in proxy authentication rules which auto login to my external gateway and this works fine if running in the console. But running as a service Fiddler still works but external gateway authentication happens.

    Has anyone used Fiddler as a service alongside a customrules.js file?

    thanks

    Gus
  2. Eric Lawrence
    Admin
    Eric Lawrence avatar
    833 posts

    Posted 05 Nov 2014 Link to this post

    Hi, Gus--

    Fiddler is not designed for service use; you typically should consider building a FiddlerCore-based application instead. This ensures that your code fully controls the UI and you don't end up in a situation where the service is deadlocked on some UI that cannot be responded to.

    Having said that, when running from the service account, Fiddler looks for its CustomRules.js file in the service account's \Documents\Fiddler2\Scripts folder, not your account's folder. So you'll need to copy the script to the correct folder.

    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. Gus
    Gus avatar
    3 posts
    Member since:
    Nov 2014

    Posted 06 Nov 2014 in reply to Eric Lawrence Link to this post

    Thanks Eric,
    I have setup the service with a "logon as" setting, this is set to the account that I usually have Fiddler running successfully under.
     
    ie.
    I can login as "user1" and the fiddler app runs perfect with my customrules in the default location, and my base64 credentials setup and all client access works ok, with proxy-authorization taken care of. EG my clients are not prompted for a user/pass when accessing the external gateway.
     
    If I run Fiddler as a service with "logon as" set to the same user above "user1" I cannot get client requests to work. They are simply prompted for credentials to the external gateway.
     
    I hope I am making sense!
    thanks
    Gus
  4. Eric Lawrence
    Admin
    Eric Lawrence avatar
    833 posts

    Posted 06 Nov 2014 Link to this post

    Is "User1" logged in more than once?

    If you run Process Monitor and watch for reads of the CustomRules.js file while restarting the service, what do you see?

    How, specifically, are you attempting to add proxy authentication to the requests?

    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.

     
  5. Gus
    Gus avatar
    3 posts
    Member since:
    Nov 2014

    Posted 07 Nov 2014 in reply to Eric Lawrence Link to this post

    Thanks Eric,

    my user1 account is not logged in. the server has no logins from user connections.
    I will run the process monitor and watch the customrules.js file

    Re. proxy requests in my rules file...my external proxy uses basic auth. I can use the bas64 text tools in fiddler to convert my username:password combo to base64, which allows me to add the following to:

        if (m_AutoAuth) {
                   oSession.oRequest["Proxy-Authorization"] = "Basic dXNlcjE6cGFzc3dvcmQ=";
            }

    This works perfect if running Fiddler in the console and not a service.
    I will get back re. the process monitor.
    cheers
    Gus
  6. Eric Lawrence
    Admin
    Eric Lawrence avatar
    833 posts

    Posted 07 Nov 2014 Link to this post

    Just to be clear, you've defaulted m_AutoAuth to true, right? :-)

    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.

     
Back to Top