Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 16075 invoked from network); 20 Jun 2006 00:13:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Jun 2006 00:13:47 -0000 Received: (qmail 20144 invoked by uid 500); 20 Jun 2006 00:13:46 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 20121 invoked by uid 500); 20 Jun 2006 00:13:45 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 20090 invoked by uid 99); 20 Jun 2006 00:13:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Jun 2006 17:13:45 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of sebbaz@gmail.com designates 66.249.82.204 as permitted sender) Received: from [66.249.82.204] (HELO wx-out-0102.google.com) (66.249.82.204) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Jun 2006 17:13:44 -0700 Received: by wx-out-0102.google.com with SMTP id t16so883336wxc for ; Mon, 19 Jun 2006 17:13:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FzniMn2wz7a9xOek7EbaSacj5wjxrfzxsS/92Lr1NFtmNjFPTAY31WvzHEIv58aM064iKgwatvhCc7PKwZ5BRi0fqmr2h2dlYlFINOjXntCssh+L0H6GRZLVsVWE7JnRmPL0rTOr8CYdwIsgfqhyS5SyndDiZOtZHq9nm3PPngU= Received: by 10.70.8.15 with SMTP id 15mr9506661wxh; Mon, 19 Jun 2006 17:13:24 -0700 (PDT) Received: by 10.70.91.4 with HTTP; Mon, 19 Jun 2006 17:13:24 -0700 (PDT) Message-ID: <25aac9fc0606191713l3d173859s7644279be188bba9@mail.gmail.com> Date: Tue, 20 Jun 2006 01:13:24 +0100 From: sebb To: "JMeter Users List" Subject: Re: & in dynamic links In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <25aac9fc0606190150n752c4712n34a062d200f98c1b@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 19/06/06, Bennett McElwee wrote: > >> Go > > Are you sure it's not valid? > > Quite sure. Any ampersand appearing in a text node or an attribute is > interpreted as the beginning of an entity reference (e.g. "). > Therefore if you want an ampersand in text or in an attribute (such as > an href), you must encode it as & (or the equivalent Unicode code). > Thanks - still learning ... I'd assumed that the quotes protected the &, but clearly not. On the other hand, the snippet: a < & &; > &# passes, so perhaps it's not always necessary to encode &. Given that one might actually want to check the actual response, I think a solution would be to add an option to the RE Post-Processor to decode the response data before scanning. Clearly the HTML parsing routines need to be checked to ensure that any links etc are decoded before being used. S. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org