Thanks Michal and Mike - that did the trick. I had seen the '_g1' suffix stuff in the documentation, but it failed to register because I simply expected the variable to be the same as the result of computing the template for the replacement string of the regex function. Thinking about it I guess this provides the ultimate flexibility - I can always reconstruct the template if I need the same string elsewhere. Would it make sense to also allow the variable to be used in without the suffix (i.e. in the manner I was expecting)?
Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: [EMAIL PROTECTED] > From: "Mike Stover" <[EMAIL PROTECTED]> > Reply-To: "JMeter Users List" <[EMAIL PROTECTED]> > Date: Thu, 12 Dec 2002 11:40:06 -0500 > To: JMeter Users List <[EMAIL PROTECTED]> > Subject: Re: Reusing the result of a regex in the same request > > It's actually quite common to want to do this, I've found - particularly with > sites that use javascript, pop-up windows, etc. > > Just for further explanation, the 'g1' part is short for "group #1". Group 0 > is a built- in group that refers to whatever the entire regular expression > matches. > > -Mike > > On 12 Dec 2002 at 13:59, Michal Kostrzewa wrote: > >> >>> >>> HTTP Request >>> param1 ${__regexFunction(some(value),$1$,RAND,,,var1)} >>> param2 ${var1} >>> >> >> Please use ${var1_g1} as param2. Hovewer I've never used it in such way - I >> used previously parsed value in next requests. >> >> best regards >> Michal Kostrzewa >> >> -- >> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> > > > > -- > Michael Stover > [EMAIL PROTECTED] > Yahoo IM: mstover_ya > ICQ: 152975688 > AIM: mstover777 > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
