Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 22705 invoked from network); 4 Feb 2010 18:10:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Feb 2010 18:10:19 -0000 Received: (qmail 93002 invoked by uid 500); 4 Feb 2010 18:10:18 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 92954 invoked by uid 500); 4 Feb 2010 18:10:18 -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 92944 invoked by uid 99); 4 Feb 2010 18:10:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2010 18:10:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of alexjfisher@gmail.com designates 209.85.220.225 as permitted sender) Received: from [209.85.220.225] (HELO mail-fx0-f225.google.com) (209.85.220.225) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2010 18:10:10 +0000 Received: by fxm25 with SMTP id 25so804356fxm.14 for ; Thu, 04 Feb 2010 10:09:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=pRpcetCOtxIpisslDHVZvKP9K/uepEtmikBxBzSenZg=; b=GOa69O2MaQqXYsoE5Ndkqa4lwPHi3GWrQ/Aihoay2xG5ltN+xnbhcKl8V+PX4+/KO3 I/mZxQJmo9oLalCjC53vZt36WSGGxSfACNvJTN5pqtzjujmRCq9R3tA7esh3KHpPK6Ow mI+RmVfV5wD1Y4K6r+Dr9KRE4lv6/aEI4OXiw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=GNAMcgMfOhlWJ25Bqg0cM+zhwKHK3DqSxCivYF01WBaUWt9BFqJBlnOBoCgdG4JOgc 5xIKuOgQPyU2aMK0636Au8hsTEypJ+cAqhQjMzwSgTVwhZapyg8xmbMzLvEU1D7c6pmz GAMJXwg32ANpjw+B3II280HBpVFXH+VnXNp2o= MIME-Version: 1.0 Sender: alexjfisher@gmail.com Received: by 10.223.28.156 with SMTP id m28mr1584984fac.41.1265306989891; Thu, 04 Feb 2010 10:09:49 -0800 (PST) In-Reply-To: <25aac9fc1002040829x63348588ud4c23886b13f6b10@mail.gmail.com> References: <5449aac21002040807j194b0165x4dff32046737612c@mail.gmail.com> <25aac9fc1002040829x63348588ud4c23886b13f6b10@mail.gmail.com> Date: Thu, 4 Feb 2010 18:09:49 +0000 X-Google-Sender-Auth: 910d69f6d9442f64 Message-ID: <5449aac21002041009qbf30839kc401c9701f1af19d@mail.gmail.com> Subject: Re: JMeter problem with redirects From: Alexander Fisher To: JMeter Users List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On 4 February 2010 16:29, sebb wrote: > On 04/02/2010, Alexander Fisher wrote: >> Hi >> >> =A0I'm trying to test a wicket application using JMeter. >> >> =A0JMeter doesn't seem to be following certain redirects in the same way >> =A0browsers do. Specifically, I was testing logging out of the >> =A0application. >> >> =A0The wicket code for this looks a bit like. >> >> =A0public class SignOutLink extends Link { >> =A0-SNIP- >> =A0 @Override >> =A0 =A0public final void onClick() { >> =A0 =A0 =A0 =A0WicketAppSession.get().invalidate(); >> =A0 =A0 =A0 =A0getRequestCycle().setRedirect(true); >> =A0 =A0 =A0 =A0setResponsePage(SignInPage.class); >> =A0 =A0} >> =A0} >> >> =A0The logout link is to a wicket encrypted URL which then redirects to = ./ >> >> =A0If I get a redirect to http://host/wicket-app/./ I get either a 404 o= r >> =A0a web server directory listing (if listings are enabled). >> =A0Entering the same URL into firefox I get the application's sign in >> =A0page (http://host/wicket-app/) as expected. >> >> =A0Is this a known issue, or something I can work around? > > What redirect options are you using? > > If you are using redirect automatically, then JMeter does not see any > redirects, and thus won't be able to process any cookies that might be > set during the process. > This is documented here: > > http://jakarta.apache.org/jmeter/usermanual/component_reference.html#HTTP= _Request > > Try "Follow redirects"; if that fails, you will have to add the URLs manu= ally. I've tried both 'follow redirects' and 'redirect automatically'. I think it's just that the url returned in the 302 returns a different result when fetched using firefox, compared to JMeter. Could it be that firefox automatically removes all dot-slashes ('./''s) from URLs before forming the request? Should JMeter mimic this behaviour? Kind Regards, Alex --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org