Rather than use a proxy or as Bruce mentions when proxying is blocked/excluded, or when dealing with Flash, Silverlight, and Java applets, you might try this solution I used:
http://www.codeproject.com/KB/perl/webautomaton.aspx A knowledgeable person can even modify the sample parser script in that solution to generate a JMeter test plan instead of Perl based script from the HTTP traces. The generated test plan would be much like using the HTTP Proxy server and recording controller of JMeter. Without a parser, you can just manually review the HTTP traces to construct your test plan with HTTP samplers the manual way. On Mon, Oct 31, 2011 at 8:03 AM, Bruce Ide <flyingrhenqu...@gmail.com>wrote: > The only time I personally have seen this happen is when I was testing a > page that was set up in the "exceptions" portion of the browser proxy > configuration to not be proxied. Companies commonly exclude their intranet > from proxying so as to not make additional traffic on the network and proxy > servers. If you are excluding the page from proxying then your browser will > go directly to that page and not through any proxy, including the jmeter > one. > > If your browser proxy settings show any sites as being excluded, try > clearing out the "Exclusions" line and try recording again. I'd suggest > backing up that setting somewhere (Like pasting it into a text file) so you > can get it back when you're done setting up your test. I've found that it > works best for me to actually have two browsers, one which I use to record > tests and one which I use for day-to-day network access. In my case I run > Firefox off a UNIX server to record my tests. > > -- > Bruce Ide > flyingrhenqu...@gmail.com >
