Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Message-ID: 
 <7D2CDF07AA8AD511A8BA009027B12198020D2D82@exchange1.aac.academyart.edu>
From: "Zazueta, Robert" <RZazueta@academyart.edu>
To: "'jmeter-user@jakarta.apache.org'" <jmeter-user@jakarta.apache.org>
Subject: Link Parser
Date: Wed, 4 Sep 2002 10:29:58 -0700
MIME-Version: 1.0
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Hey y'all. New to the list. I just went through the archives and found most
of the answer I was lookinf for in regards to using the link parser as part
of a spidering tool (I actually *do* see some use to doing this for our
site). Everything is more or less copasetic except for one thing: it doesn't
seem to like regular expressions in the path of the HTTP Request.

Here's what I'm using:
	JDK 1.3.1
	JMeter 1.7.3
	Windows 2000

Here's how it's set up:

Root
	Test Plan
		Thread Group
			HTTP Request (Domain: my-machine, Port: 5000 Path:
/)
			Simple Controller
				HTTP HTML Link Parser
				HTTP Request (Domain: my-machine, Port: 5000
Path: .*)
			Constant Timer (3000ms)
			View Results Tree
			HTTP Cookie Manager
WorkBench

The results tree show just fine for the first HTML Request. For the second
one, though, the request data is "http://my-machine:5000/.*" and the HTTP
Response code is a Non HTTP Response Code. The HTTP response Message is --
you guessed it -- a Non HTTP response message.

Any idea what I'm doing wrong here? Thanks!

Rob Z.


--
To unsubscribe, e-mail:   <mailto:jmeter-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jmeter-user-help@jakarta.apache.org>