This topic contains 3 replies, has 2 voices, and was last updated by  Jeff Drumm 4 years, 9 months ago.

Monitoring HTTP traffic in Translator via Fiddler

  • Hi Guys,

    Is this possible? This could be more a fiddler question than an Iguana one so apologies but I thought some of the developers there would have come across this before?

    Fiddler is not able to see the HTTP traffic I am generating within the Translator so wondering if it is possible?

    Best regards,

    It’s sort of an Iguana question … Fiddler assumes that the application to be monitored supports Windows Internet Settings’ proxy configuration, and Iguana doesn’t. Or at least, configuring it to use a proxy isn’t documented anywhere I can find.

    That said, you can set the debug flag to true on your net.http.* calls to see the actual request/response data in the Translator editor and log.

    Jeff Drumm ◊ VP and COO ◊ HICG, LLC. ◊

    Well, I’m going to have to take back (some of) what I said.

    Iguana DOES know how to use a proxy … I just can’t seem to find it documented anywhere.

    Here’s how:

    From the Iguana dashboard, select Settings | System Settings | Environment Variables. Create two new environment variables, http_proxy and https_proxy, and set them both to http://localhost:8888. You’ll also need to configure Fiddler to spoof a root certificate if you’re using HTTPS (Fiddler will configure that for you as part of setting up HTTPS capture), but once that’s done, you should begin to see Iguana’s traffic in Fiddler.

    Hopefully someone from Interfaceware will chime in and endorse this as a supported solution 🙂

    Jeff Drumm ◊ VP and COO ◊ HICG, LLC. ◊

    Additional note: Just delete the environment variables once you’re done debugging …

    Jeff Drumm ◊ VP and COO ◊ HICG, LLC. ◊


You must be logged in to reply to this topic.