| || |
Loadrunner Analysis HTTPs Traffic
I am using Loadrunner 11.52 to test a mobile native application works on HTTPs.
The approach which I am planning is as below:
1. Capturing the mobile traffic (iphone) using wireshark and save it in .pcap file.
2. Passing the .pcap file to loadrunner mobile protocol to generate the script.
Please suggest me the ways in wireshark to capture the HTTPs traffic and loadrunner should generate the HTTPs traffic in to script.
Note: I have already captured the HTTP traffic in wireshark and the generated .pcap file was successfully converted in to script by loadrunner. But, I believe this wont be simple in case of HTTPs traffic.
I would also interested in knowing the other debugging tools except wireshark or other approach in loadrunner to make this job simple.
Thanks in Advance.
And why wouldn't you use proxy to capture this traffic?
I have tried using 'Proxy recording' which is introduced in loadrunner 11.52
The mobile phone and the computer running vugen are both accessing the same wifi connection
After I press record I select 'Proxy recording'
On my iPhone I have configured it to use a Manual Proxy via the Settings -> Wifi (I entered the ip address of my vugen machine in the server field and put the port as 8080)
My iPhone shows as still being connected to the wifi however I can't access the internet after configuring a manual proxy
we do not need a proxy to access the internet
Is this because of IP Conflict??????
If not, what would be the reason? Or Is the followed approach right?
Proxy was the standard recorder from versions 4.5 to 7.x for HTTP traffic. With version 8 the standard recorder for HTTP became the sockets recorder. The proxy recorder is available under the checkbox for old recording engine. Record and external application and then set your browser proxy to port 7777. For 11.52 the Proxy recorder has been updated and a new version is available on port 8080 for mobile recording.
Once you enter the proxy settings and save them all HTTP traffic (including HTTPs, SOAP and RESTful web services calls which use HTTP as a carrier) will be passed through your VUGEN proxy recorder. Until that recorder is turned on you will then have zero HTTP access to any other site. This is expected behavior if you set your HTTP proxy to a proxy service which is not yet active.