Let simulator use proxy server

Former Member
Former Member
I'm trying to debug a json request. I installed a tool (fidler) that acts as a proxy server, so I can intercept the call. The tool is setup to act as a system wide proxy server, but the simulator seems to ignore this.

So my question: how can I force the simulator to use a proxy server?
  • You can usually enable the proxy server in your system settings. On windows it is in Control Panel > Internet Options > Connections > LAN Settings.
  • I tested this with Fiddler as well and as you I could not see requests/responses. Exclipse has proxy settings in Window > Preferences > Network Connections - and this seems to detect ok when Fiddler sets system proxy to its own local proxy. The simulator/ConnectIQ must use its own settings that disregard the system proxy it looks like.

    Also Java (if that is relevant) is set to use system proxy by default - no help here.

    By research I found that you can use Wireshark to see the network communications, this tools is much more low level and in some cases could be difficult to read because of many packets, you have to set filter to 'http'. A makeJsonRequest call will result in two Http protocol packets (request and response) and once you've found them they are easy to drill into including the json object.
  • You can usually enable the proxy server in your system settings. On windows it is in Control Panel > Internet Options > Connections > LAN Settings.


    Yep, that should do it! Not tried it myself, but it makes sense. I'm about sure it's the same path on all current windows though, as Vista could be different than Windows 10.... (we all HOPE they are different ;) )
  • FYI, I've used tcptunnel successfully in my testing. You should also be able to use netcat
  • Former Member
    Former Member over 9 years ago
    You can usually enable the proxy server in your system settings. On windows it is in Control Panel > Internet Options > Connections > LAN Settings.

    That's what I did, but this didn't work.

    By research I found that you can use Wireshark to see the network communications, this tools is much more low level and in some cases could be difficult to read because of many packets, you have to set filter to 'http'. A makeJsonRequest call will result in two Http protocol packets (request and response) and once you've found them they are easy to drill into including the json object.


    I'll try that, thanks.