5.1 - Traffic Traffic — 05 - Traffic documentation. Traffic Recorded Note: The legacy Traffic workflow has been replaced by Instant Replay. The articles in this section document the original Traffic workflow for reference and legacy environments. For the current network traffic capture and replay capabilities, see Traffic - Instant Replay. Legacy Traffic Workflow What was Traffic? Traffic was Appvance IQ's HTTP traffic recorder. It provided an alternative to Appium-based testing for load and performance testing of mobile applications by capturing and replaying application network traffic rather than interacting with the application UI. AIQ used an HTTP proxy to capture traffic from a browser or mobile device and convert the captured requests and responses into a HAR script. The resulting HAR script could then be replayed as part of a performance or load test without requiring the test flow to be implemented manually. How did it work? The legacy Traffic workflow consisted of three main steps: Connect - configure a browser or mobile device to use the AIQ HTTP proxy. Record - perform the actions to be tested while the proxy captured the network traffic and mark meaningful steps, such as "Login" or "Purchase." Analyze - save the captured traffic as a HAR script and generate reports for analysis. The resulting HAR script could then be used in a scenario for performance or load testing. Example For example, a team could load-test the login flow of a mobile banking application by connecting a mobile device to the AIQ proxy and recording the login process. AIQ would capture the HTTP requests generated by the application and produce a HAR script that could subsequently be replayed with multiple virtual users to evaluate server behavior under load. Current Workflow For new implementations, use Traffic - Instant Replay instead of the legacy Traffic workflow. Instant Replay captures network activity while recording UX tests in Test Designer, providing the current approach for combining UI test recording with network traffic capture and replay. Legacy Prerequisites The following prerequisites applied to the original Traffic workflow: An AIQ instance with the legacy Traffic feature enabled. A browser or mobile device that could be configured to use the AIQ HTTP proxy. The proxy port reachable from the browser or device. An SSL certificate installed on the device when HTTPS traffic needed to be captured. Sections in this book Current workflow Traffic - Instant Replay - captures network activity while recording UX tests in Test Designer and replaces the legacy Traffic workflow. Legacy workflow Traffic - Connect - configure the proxy and connect a browser or device. Traffic - Record - capture HTTP traffic and mark steps. Traffic - Analyze - generate reports from captured traffic. Traffic - Running a Complete Scenario - end-to-end example using the legacy Traffic workflow. Device setup Android - Proxy Settings Android - Installing Certificates Android - Bypass Proxy Exceptions iOS - Proxy Settings iOS - Proxy Settings and PAC Files iOS - Generating Certificates Security and troubleshooting Traffic - Managing SSL Certificates Browsers - Bypassing HSTS Warnings Last reviewed: August 2026 This documentation describes the legacy Traffic workflow. For the current implementation, refer to Traffic - Instant Replay. Traffic - Record On the Connect tab, once the port and the device are configured to listen to the traffic - it is time to move to the Record tab to record all the HTTP traffic of the target application. When you provide a port that is already in use on the system, AIQ will prompt an error saying "Port is already in use, choose a different port" Once recording has begun, the port fields are disabled and can no longer be changed. Record Tab: Mark Step: Before starting the proxy, the user should mark the step by providing a meaningful name to the set of requests the HTTP proxy is going to capture. For example, the user can mark the step as login - the steps/requests that can be captured below the login would involve the following: a. Click Log in to go to the login page b. Set the user name and password c. Click Log in to navigate inside the application All this traffic can be captured below the log-in step, After marking the step and starting the proxy, all the traffic mentioned in the above use case will be saved under Log in Step. The next step would be to Purchase a. After successful login, click some items b. Add them to the cart c. Click purchase All these can be marked as another step by providing the step name as Purchase and clicking on the Mark step, these can be validated using the status tab. Record: After marking a step user can click the Record button, a confirmation message will be displayed informing that the proxy is starting on the provided port number. The record button will be grayed out. Pause: At times it may be required to pause the ongoing recording of the traffic as the user might want to do some unwanted navigation which anyone would want not want to have in the recorded script, Pause Recording request can be used for this purpose. The pause button would be changed to 'Resume' after clicking Resume: Once the Pause recording request has been chosen, the user would want to resume the recording after pausing the script for which the Resume button could be used. Stop: Stops the Recording of the HTTP Traffic. Clear: As the name suggests it just clears the recorded traffic requests, users can use this when creating new scripts. Refresh: Can be used to refresh the HTTP Traffic calls. Save: Once you are done with recording the traffic requests, you can click the 'Stop' button and click the Save button which will open the file manager and saves the script which will have the .har extension. You also have an option to remove unwanted calls recorded, using the Delete button available for every request. Status: Displays the status of the proxy, either Running or Not, and also the recording status or being running, paused, etc. Use the refresh button periodically to capture all the latest traffic logs before saving the HTTP file. Related: The Traffic recorder has been replaced by Instant Replay, which captures network activity while recording UX test cases in Test Designer. Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Traffic - Analyze The last step is the Analyze step. Once the HAR script is saved, click the Next button. Saved HAR Script would be auto-populated. Click Analyze HAR Script button for the report to be generated. This will generate the following reports: Requests per Domain Report - groups the captured requests by domain, so you can see how much traffic each domain received. All Domains Report - shows the overall traffic captured across all domains. Headers Report - lists the request and response headers captured in the traffic. Sessions Report - shows the captured traffic organized by session. You can also analyze any existing HAR file by navigating to the Analyze page and browsing the HAR file and clicking 'Analyze HAR Script' to generate the report. You can also download the full report in PDF Format. The sample report can be downloaded from here. Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Run a Complete Traffic Scenario in AIQ Last reviewed: September 25, 2026 Use this article when validating a full Traffic scenario from setup through execution and result review. What changed in this article Clarified the sequence from traffic preparation to run execution and review. Added pre-run checks for target availability, data readiness, proxy/recording setup, and expected completion criteria. Added post-run checks for output, errors, captured transactions, and report readiness. Validation workflow Confirm environment, data, and traffic capture settings before starting the scenario. Run the full scenario and monitor output for early failures. Review transactions, errors, and results before marking the scenario ready for reuse. Review note: Reframed this as an end-to-end Traffic scenario checklist instead of a generic “run scenario” page. Last updated: September 25, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Browsers - Bypassing HSTS Warnings Sometimes the browser will show an HSTS warning message Some browsers use HSTS (HTTP Strict Transport Security), which lets a web app remember that it should only be accessed over HTTPS. When this happens, the fix is to clear the browser cache. Open the Privacy settings in Firefox and clear your recent history: Now the Cache and Active Log-ins with a Time range to clear set to Everything and Click Clear now. As a last resort, you can fully disable HSTS in Firefox: Type about:config in the Firefox address bar. A warning may appear; click OK. In the list of preferences, look for network.stricttransportsecurity.preloadlist, right-click it, and toggle it to false. If the preference is not in the list, right-click anywhere on the page, select New > Boolean, name it network.stricttransportsecurity.preloadlist, and set it to false. Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Traffic - Managing SSL Certificates When using SSL, the user must accept the certificate manually in Firefox and Android Adding security exception to Firefox In the output log, AIQ will show the URL that needs to be entered in the browser to accept the certificates Full SSL Support - adding the root certificate When full SSL support is required (avoid warning messages) the user needs to install the root certificate (certificate.cer) that is created by the user. The certificate has to be installed in the device which will connect to the proxy. The certificate can be added to Android, Windows, Mac, and iPhone. The certificate password is appvance. Read Installing Certificate for more details on creating the certificate. Installing the certificate on Windows: Double click the certificate and press next Type password appvance and click next and finish Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Traffic - Connect Configure Traffic Connect for AIQ Traffic Capture Last reviewed: October 2, 2026 Use this article when configuring Traffic Connect so AIQ can capture or route traffic for supported testing workflows. What changed in this article Expanded the short title into a configuration-focused Traffic Connect article. Added checks for network route, proxy/certificate setup, target application reachability, device or host source, and captured evidence. Added troubleshooting guidance for no-traffic, partial-traffic, and certificate-related capture issues. Validation workflow Confirm the traffic source, target application, network path, and certificate/proxy requirements. Start Traffic Connect and verify AIQ can see expected requests without capturing unrelated sensitive traffic. Run a small capture and review output before using the configuration for a full test. Review note: This page now gives an operational setup workflow instead of a vague traffic feature label. Last updated: October 2, 2026 If you have feedback on this topic, contact documentation@appvance.ai. iOS - Proxy Settings On your iOS device, Go to Settings Click Wi-Fi Connect to the same network as AIQ is running. Select the info (i) button Scroll down to the HTTP Proxy section and select Auto Edit the URL and add the URL of the iphone.pac file: NOTE: important the http:// is mandatory, if missing the proxy will not receive any traffic Go to Manual, provide the Server (the IP address of the machine where AIQ is running) and the Port number (9095), the same port number provided in AIQ HTTP Proxy. http://:8080/Appvance/iphone.pac It might be necessary to hit the link “Renew Lease” if you see that it takes a while for the Wi-Fi connection to apply to the iphone.pac file Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai iOS Proxy Settings and PAC Files for AIQ Traffic Recording Last reviewed: September 25, 2026 Use this article when configuring iOS devices to route traffic through AIQ recording or proxy infrastructure. What changed in this article Standardized “IOS” to “iOS” and tied proxy/PAC guidance to AIQ traffic recording. Added checks for Wi-Fi network, proxy host/port, PAC file URL, certificate trust, and app traffic behavior. Added a warning that VPN, MDM, or corporate network policy can override manual proxy settings. Validation workflow Connect the iOS device to the intended Wi-Fi network. Configure manual proxy or PAC URL and confirm the device trusts any required recording certificate. Open the target app or website and confirm traffic appears in AIQ before recording a full flow. Review note: Made the mobile proxy setup more actionable and called out common iOS/network-policy blockers. Last updated: September 25, 2026 If you have feedback on this topic, contact documentation@appvance.ai. iOS - Generating Certificates Make sure AIQ services are running on the instance by navigating to "http://server-name:8080/". Go to iPhone Click the link and install the certificate. Go to Settings Click Profile downloaded You will see the Appvance 2020 Certificate Click Install and Accept, the certificate would be installed successfully Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Android - Proxy Settings On your Android device Select your network and click Manage Network settings. Check Show advanced options Type proxy host and port, it could be a local server For Setting the Proxy in Android, using mobile data: Go to settings, mobile networks Click Access Point Names and type Proxy host and Proxy port. The proxy server should be accessible worldwide Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Android - Installing Certificates Click the link to download the certificate Copy the certificates to the android and go to Settings/Lock screen and security Click Other security settings (at the bottom) Click Install From Device Storage Select certificate.pfx and click DONE Type password appvance Select Use for VPN and Apps and click OK Repeat the process and select Wi-Fi and select OK Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Android - Bypass Proxy Exceptions Some services running in the background can affect the recording. To prevent this, filter them in Android by adding the following domains to the bypass proxy list (and very likely some more domains specific to your environment): *.google.com, *.googleapis.com, *.localytics.com, *.microsoft.com, *.pipe.aria.microsoft.com, *.google-analytics.com, *.accuweather.com, *.uservoice.com, *.flurry.com, *.weather.com, *.crwdcntrl.net, *.w-x.co, *.acompli.net, *.g.doubleclick.net, *.adnxs.com, *.services.mozilla.com, *.gstatic.com Last updated: June 26, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Traffic - Instant Replay Note: Instant Replay replaces the Traffic feature. The Traffic HTTP proxy workflow (Connect, Record, Analyze) has been superseded by Instant Replay, which captures network activity while recording UX test cases in Test Designer. How about Recording Network activity in the background while you are recording your UX test cases using Test Designer? Test Designer Instant Replay is the answer. Yes, Test Designer Instant Replay can capture all your network activity while a use case is getting recorded in Test Designer and it can be exported as a .zip (with HAR and contents of the page), CSV file that has details of the method, port, vhost, uri, status and also as an executable JS file. API Testing Process: When an API request is done, Test Designer tells the browser to do the request, but it injects a header to capture and provide the API calls. With the option, Exclude requests matching the following regular expressions (comma separated): with default values of (.*\.(jpeg|png|gif|bmp|svg|css|js|gif|woff2|jpg).*), will filter out all those files with the mentioned extensions, you can remove or add or make any changes to these extensions depending on the requirements. Navigation: From the dashboard page, Under Record, Click Test Designer Instant Replay. File Menu: Open: Only allows .zip files. When you save the file after having some traffic recorded, File > Saving will save the file with a .zip extension or when you do a File > Export to HAR, it will save with a .zip extension. File residing in the local machine can be opened using File > Open. Save: Is used to save the file after changes or a new unsaved file. Save As: Is used when you want to do a Save As of an already opened file with a different file name. Comparison Report: Two Instant replay zip files can be compared to check the differences between the Response body, Headers, Payloads. Typically used for the same type of flows, with different login details, or with different environments to check the differences between Response bodies, headers, or payloads. Export : Comparison Reports To generate the comparison report, you first need to load the instant replay file to compare against baseline data by making use of File > Open and open the zip file that is saved as the instant replay of the script. Click File and choose Comparison Report from the Drop-down. API Comparison pop-up would be displayed to choose the baseline data to file Instant Replay (.zip file) with the Browse button. Maximum payload size (chars): would default to 4096 chars but that is something that can be changed and allows only numerical entries. Start Comparison button would be enabled, clicking which will download a zip containing all the reports. It is required to extract the downloaded zip content of the files and open the generated .html file. Below is the comparison report that is going to be generated, which will show the comparison report file name, the files that are used for comparison, and the maximum data size. It displays all the Requests along with the size, Response Body and the differences for each of the rows which can be expanded/collapsed, Headers and request/response header differences which can be expanded/collapsed for each of the rows, Payload with differences for each of the rows which can be expanded/collapsed. There is an option to hide or show the row numbers. Also, the option to choose a particular column that needs to be displayed. You can click each of the buttons like "response headers diff" for example to check the differences. "-" means no data found The green color means some data has been added The red color means some data has been removed or not found 6. Export: The recorded traffic can be exported to 3 different formats. a) HAR: downloaded as a .zip file, contains the har calls "Record.har" plus all the history containing .jpg's, .html's, txt's, .dat's, .json files etc b) CSV: Contains details of the method, port, vhost, uri, status. This CSV can be used as a log from Appvance AI as well c) JS: A executable JS Script with all the gets and posts like the one below Actions Menu: Start Recording: will start recording HAR traffic for the app that will be recorded using Test Designer IDE. Re/Start Playback: will clear the historical data which is already present and make a fresh recording of the requirement for playback. Stop: will stop recording HAR traffic calls. Clear History: will simply clear your recording area and it will be ready to record new HAR traffic. Show calls: This is more like a refresh button, that keeps updating the new traffic that got recorded. Status: You will see Status on the top right corner of the page, Initially Status will be Standard. When you click Start Recording from the Action menu bar Status will change to Record, and Again, Status will be Standard when you click Stop from the Action menu bar. How to use Test Designer Instant Replay Follow these steps: Go to Instant Replay and click Start Recording from the drop-down. Go back to Test Designer IDE and begin Recording by clicking Record > choose a browser and perform your UX actions. Come back to Instant Replay and click Show calls from the Action Menu, you will notice all the traffic that is getting captured. Once done with all the recording, you can go ahead and save the file as a .zip file or any other 2 formats mentioned above. Not just recording, Test Designer Instant Replay also records the history calls when we playback scripts from Test Designer. Go back to Test Designer IDE, open any existing script, come to Instant Replay, click 'Start Recording' and playback the script from Test Designer IDE, and you can click 'Show calls' from the Action menu, you will notice all the traffic that it got created. These traffic logs can be used to generate more traffic when running as a performance test (running at the protocol level) using along with the actual Test Designer script (running at the browser level). Last updated: August 28, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai