Thank you for the reply. Here's my test plan:
Test Plan
Thread Group
Recording Controller
View Results Tree
HTTP Authorization Manager
HTTP Request
Browser-derived headers
Regular Expression Extractor <-- grabs id,
assign TESTID variable
HTTP Request <- Path field has
http://server/subdir/${TESTID}
I view the Results Tree and looked at 2nd HTTP Request data - it shows
"http://server/subdir/${TESTID}". TESTID should resolve and contain a value
extracted by Regular Expression Extractor but it doesn't. Grrrrrr... If I
put ${TESTID} in the Parameter section in the 2nd HTTP Request, it resolves
to the value extracted by "Regular Expression Extractor".
My OS is NT 4.0 SP6 and JMeter.bat dated 8/17/2003 v.1.9.1
Lastly, if I added a "HTTP URL Re-writing Modifier" with "Path Extension"
checked, ${TESTID} does resolve in the Path field but it adds the ";" at
end, which is an invalid URL. Sigh... Please help.
Thanks again,
/peter
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 11, 2004 6:58 PM
To: JMeter Users List
Subject: Re: Variables ( ${..} ) not resolving in HTTP Request - path
field
Works for me in the current CVS release.
Also works for me in 1.9.1.
Please can you post a simple test case to Bugzilla?
----- Original Message -----
From: "Lay, Peter" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 11, 2004 10:04 PM
Subject: Variables ( ${..} ) not resolving in HTTP Request - path field
Hi All,
I successfully extracted a value from a previous response and assigned it to
a variable. The variable is resolved in the Parameter section of HTTP
Request but not in the Path field. It seems it gets resolved everywhere but
the Path field - I tried it on the Server Name and it works but not in the
Path field. Any help is appreciated.
Thanks,
/peter
**************************************************************************
This e-mail and any files transmitted with it may contain privileged or
confidential information. It is solely for use by the individual for whom
it is intended, even if addressed incorrectly. If you received this e-mail
in error, please notify the sender; do not disclose, copy, distribute, or
take any action in reliance on the contents of this information; and delete
it from your system. Any other use of this e-mail is prohibited. Thank you
for your compliance.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]