On 24/07/06, Jaw Dat <[EMAIL PROTECTED]> wrote:
On Sun, 2006-07-23 at 17:13 +0100, sebb wrote:
> >
> > Why is this the case, and is what i'm trying to do possible
> > in jMeter ? (ie, record all the pages i visit and capture the
> > parameters sent to those pages?) Because this would save me
> > having to collect form inputs by parsing the HTML source of those
> > pages. I hope i'm phrasing my question clearly.
>
> Sounds like the pop-ups are being generated locally by the browser,
> and do not involve any interaction with the server.
>
> The JMeter proxy can only capture requests actually sent to the
server.
>
Even though the popup is indeed generated by a javascript function,
window.open(URL,...) , this surely results a request sent to the server,
since the URL refers to the jsf to be opened in the popup. So why
Agreed.
should this escape the JMeter proxy? What's the workaround?
As I said previously - perhaps Javascript does not use the proxy
(unlikely) or perhaps you have accidentally filtered out the request.
> Have you set any filters in the proxy? It's easy to accidentally
exclude pages.
>
Yes. The include filters are :
.*\.jsp
.*\.jsf
.*\.htm
.*\.html
.*\.php
The excludes are :
.*\.jpg
.*\.gif
.*\.png
I suggest you try allowing everything through until you have got the
script working.
> [Could Javascript can be used to download pages directly from the
> server bypassing the proxy? This would explain what you are seeing,
> but seems a broken design to me.]
>
Very good question. This is the important question now actually. If it
is the case, then wouldn't this be a problem on the part of JMeter?
In any case, how to overcome this?
No, if Javascript bypasses the proxy when it is downloading pages,
then that is a feature of Javascript, not JMeter.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
