Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 99364 invoked from network); 12 May 2009 15:04:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 May 2009 15:04:51 -0000 Received: (qmail 3867 invoked by uid 500); 12 May 2009 15:04:50 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 3840 invoked by uid 500); 12 May 2009 15:04:50 -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 3821 invoked by uid 99); 12 May 2009 15:04:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 May 2009 15:04:50 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jose.sarco@gmail.com designates 209.85.219.176 as permitted sender) Received: from [209.85.219.176] (HELO mail-ew0-f176.google.com) (209.85.219.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 May 2009 15:04:42 +0000 Received: by ewy24 with SMTP id 24so37098ewy.37 for ; Tue, 12 May 2009 08:04:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=B1OZiGDjgZ7IefEvkz633YNbL+lG3RQpspb1OWMdWW8=; b=Bedm2RjKfve6ySFnlus0kX5yqUA928/cIupWcuc9nEfjO5awRdi5JfTZoFa7fDF7Nh RiBmXhePmRZ+S6r0/Qy5ljpSHRW4RQ9YmxD2DPs5Y9d8N/AYie8EI1z/CKGAhMpBBV87 Ij+vo3R4Sx5xORy6jZOCGTp15oscNHk+mFfTQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=G3T2S5DuUut2qrw8qI3It/JYnxG9aHeWxDeyNnva54mITjlJY5m9jx3VKUFF7cPlTk lBYu3EviIs3hdXR3kWtSgski9mxCnovOhpLvg6lHvDMEH0ZtzRlC79DtSzZM9vxTj4kz +FX8ildY+H2OmelwNZfyIE41jr+q0nrWNifH4= MIME-Version: 1.0 Received: by 10.211.180.9 with SMTP id h9mr928658ebp.6.1242140660945; Tue, 12 May 2009 08:04:20 -0700 (PDT) In-Reply-To: <525a8f740905120724h45f10c82x74673a290cb1d938@mail.gmail.com> References: <525a8f740905120724h45f10c82x74673a290cb1d938@mail.gmail.com> Date: Tue, 12 May 2009 16:04:20 +0100 Message-ID: <29ac57aa0905120804q43b0bd2bpc5f5aff234d8eef5@mail.gmail.com> Subject: Re: How to handle jsessionid as path parameter instead of cookie in JMeter? From: Jose Pablo Sarco To: JMeter Users List Content-Type: multipart/alternative; boundary=000e0cd1ff00db53db0469b8684a X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd1ff00db53db0469b8684a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Do you tried with Regular Expressions? You can extract the jsession value from the URL and then use it as parameter.... I hope it helps. On Tue, May 12, 2009 at 3:24 PM, Nguyen Dao wrote: > Hi everyone, > > *MY PROBLEM:* > The JSF application on Tomcat 5.x that I have been asked to load-test > disables cookie; it gets the jsessionid from the path parameter. > > When a user hits a protected resource, he/she is directed a login page > whose > url is appended with ";jsessionid=somehexvalue". This jsessionid will then > be appended to all following requests. Submitting a request with a > different jsessionid value will cause a new login session. > > As such, the "HTTP Cookie Manager" Config Element can not be used. > > *QUESTIONS:* > Is there another Config Element that I could use? > Any suggestions? > > Thank you, > Nguyen Dao > mr.nguyendao@gmail.com > --000e0cd1ff00db53db0469b8684a--