I am learning JMeterProxy using WAMP and opencart web app.I did a recording using HTTP Proxy Server. I configured firefox and recording went smoothly. But if i am using IE, nothing seems to be recorded. I added a tree view listener in HTTP Proxy to log the recording, nothing is logged in it when i am using IE.
Some observations:
when i stop recording and if i try to access the local site using FF, it is not accessible, but in case of IE i could open the site.
If i browse an external site, recording is working.
I am accessing my site as http://localhost:81/opencart/index.php, since 80 port is used by IIS
My question is.
How would i trouble shoot this kind of scenario.
What changes i should i make in IE proxy settings.
I solved this problem, Here is the solution, as per JMeter documentation
If JMeter does not record browser URLs such as http://localhost/ or
"http://127.0.0.1/", try using the non-loopback hostname or IP address,
e.g. http://myhost/ or "http://192.168.0.2/"
So providing the host name in place of loop back address solved the problem
Related
I have an application installed on my machine for learning purposes. Its URL is http://Localhost:8080/*****. JMeter fails to record the requests whenever I use the URL above. If I replace "localhost" with the machine IP, JMeter records without any issues. Loadrunner can record both URLs.
Is it a bug or is the JMeter proxy setting designed in that way?
Thanks...
JMeter doesn't filter loopback URLs, however you browser can do this, at least latest Firefox does:
As per How to Run Performance Tests of Desktop Applications Using JMeter article you might also need to install Microsoft Loopback Adapter
And last, but not the least, the application, browser and JMeter might be looking into different protocols: IPv4 and IPv6, you need to ensure that your localhost hostname resolves into the same IP address for all 3 components.
Latest version of Firefox by default does not allow localhost or 127.0.0.1 to be proxied.
After searching a lot online, finally the following steps worked for me:
Enter about:config in the Firefox URL bar
Search for config network.proxy.allow_hijacking_localhost using the search box and toggle its value to true
Now try recording scripts in Jmeter from localhost related webpages.
Note:
I am using Firefox 80.0.1 (64-bit) and Apache JMeter 5.3
I found reference from Setup JMeter proxy to record activities on a local web application
Please find the about:config page for Firefox browser below.
I can't able to record jmeter using with proxy server.
I tried proxy settings in RUN command jmeter.bat -H 192.168.61.202 -P 8080.
Jmeter is recording with the browser actions, but not connecting the internet.
Showing error page on browser.
See the screenshot- Error shown in browser
are you able to record it using normal browser mode? If yes you should check for the firewall and add the specific port numbers to exclusions as some time back I faced the same issue, after i added the port number to excluded in Inbound and Outbound rules and disabling the antivirus setup on my machine made it work
Testing out Ghostlab on mobile presented an issue when the locally hosted page attempts to ping another locally hosted page via AJAX. Normally, GhostLab will rewrite the URL for you, but since it's an AJAX request I'm assuming it's not rewriting it because it's a dynamically generated URL.
Works fine on virtual machines and host machine with modified HOST file. Fails to load AJAX. The proxy server settings are very limited on GhostLab. Has anyone come across this issue and solved it?
The solution is to run another proxy server because you can't really modify the HOST file on iPhones or Androids without a huge headache.
I ended up using Charles Proxy. I remapped the locally hosted URL to which it was making the AJAX call to my local machine and it fixed everything. Here are the instructions:
1) Open Charles
2) (Menu)Tools/Map Remote...
Add the url you are local hosting to remap any traffic going through Charles Proxy to go to your machine See image example:
Do the same to any other subdomains or domains that are locally hosted on your machine and remap them too.
3) On your mobile device, open settings and select your local Wifi Network.
4) Change the proxy to your machine's IP address and relevant PORT.
5) Attempt to access the website and Grant permission via Charles.
This should fix it all.
This issue is occurring in a C#, .NET 4.0 environment. I tried using Fiddler but it doesn't show up. After searching around, the suggested solution was to change the address of the request from localhost to the machine-name.
This worked on my local machine: after changing the call from localhost to my-machine, fiddler picked it up. The real issue is on a client's staging environment with production code. I can not modify the code there to take this change.
Note, as far as I know, on the client site it should be making the request out to the host name and not localhost anyways.
Also, on my local machine I actually hit localhost in my browser, and it seems to pick those up fine. Just not the request built in code. Why is that?
Thanks!
It sounds like you're saying: "This works fine on the client's PC but not on my dev PC when using Localhost." Is that correct?
In IE9, I changed WinINET to enable Fiddler to capture loopback traffic from the browser. Sadly, the .NET Framework hasn't yet adopted support for the <-loopback> token, which means that traffic sent to 127.0.0.1 or localhost bypasses the proxy.
I made a proxy server,and I'm testing it using a client name Proxifier.
I made the first part with autentication to work,but i don't know what to do next.
I called Connect() an the address received from the client,but that is from a webpage.
So i need to connect to the webpage? What next then? I can't browse the net with the proxy on.
So i hope someone could help me an what to do next.Thanks.
to test a proxy server is simple as these.
In your browser, configure the proxy settings to the ip:port of your proxy server, in these case if you are testing on local machine, your ip is 127.0.0.1 and you are listening on port 80.
browse a webpage mostly google with the browser and see if it loads properly, if it does, then you proxy server is working