A SOASTA Conductor acts as an available proxy whenever it is installed on a given machine on a public network. If that network is ma mobile network, then HTTPS recording can be accomplished from the mobile device using the Conductor as the mobile device proxy.
Conductor proxy configuration on an iPhone
To configure an iPhone to use a Conductor as a proxy:
- In Settings, Ensure that WiFi is set to "On" (you may want to put the iPhone in Airplane mode and just enable wifi).
- Select the blue arrow to the right of the WiFi where the Conductor is installed. The Wi-Fi Networks > <network name> page appears.
- Scroll down to the HTTP Proxy section and click the Manual tab.
- Enter the IP address of the Conductor proxy server machine. For example, 192.168.1.114 : On Mac, you can look at the Info tab in "Network Utility" to determine your IP.
- Enter the Conductor proxy port. The default is 4440. If the Conductor was installed with another port, enter that port number instead. You can check Conductor Preferences "HTTPS recording port" to determine port.
- Install the .cer file (Changing SOASTA Conductor ) to enable HTTPs recording. You will need to unzip the zip file first. The .cer file is installed by accessing the .cer file in a browser or email on the iPhone device itself. The iPhone will walk you through installing it on the device.
- Start the recording in CloudTest. You should see protocol traffic recorded.
Conductor proxy configuration (using bogus proxy settings)
In some cases, a spoofed or bogus mobile proxy configuration can be set up in order to distinguish between a proxy-related and an app-related debugging issue. For example, this procedure is recommended whenever HTTP(s) recording appears to be working, but some or no messages appear in the Clip Editor while recording.
- In the device proxy settings, set bogus proxy parameters.
For example, www.example.com using port 12345.
- After setting up the bogus configuration, run the application and observe it.
- if the application works as expected, it means that the application ignores the device general proxy settings and should be fixed.
- if the application cannot connect to the server, than this issue requires more troubleshooting.