Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 65691 invoked from network); 22 Apr 2010 17:22:03 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Apr 2010 17:22:03 -0000 Received: (qmail 78855 invoked by uid 500); 22 Apr 2010 17:22:02 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 78832 invoked by uid 500); 22 Apr 2010 17:22:02 -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 78824 invoked by uid 99); 22 Apr 2010 17:22:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Apr 2010 17:22:02 +0000 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shettyd@gmail.com designates 209.85.212.172 as permitted sender) Received: from [209.85.212.172] (HELO mail-px0-f172.google.com) (209.85.212.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Apr 2010 17:21:56 +0000 Received: by pxi19 with SMTP id 19so753531pxi.31 for ; Thu, 22 Apr 2010 10:21:35 -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:received:message-id:subject:from:to:content-type; bh=Mpm/XYsUnJfBUPneNSbEeZIklUfTWkVu2UhAb0F6BXE=; b=dxAXeizEHiL+khvmw1yyHWUrtuViV1hYnLRbXs7QOcUTDvwauFeNI/EuH2PHdAdOhg Wxz4l6dTP2jpjYzcRxTXhfaWZZsov1avbQiBFeJO+HZ7HskJpGuhQ78XJ56R9VbiREuN iU35abVIEhujCZAZLPhSpgl9lhL1OQ8HFskrg= 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=gTpV2ihQ5l6C00v53sZnQ+NkzcCssDEt1nz8mQxpd1/J+ADBCJFo1ZBlfjGz8zuLid Qw8LpRtKc4xg1JObwFt4l3qUhr02sMiESgeXnEah3g37xsh9ODrtgE/JICLfrwzg2ZVg IH6WZ03H1n+OpCWttSKBGfgIp5kmVSagvudEM= MIME-Version: 1.0 Received: by 10.140.255.21 with HTTP; Thu, 22 Apr 2010 10:21:35 -0700 (PDT) In-Reply-To: References: Date: Thu, 22 Apr 2010 10:21:35 -0700 Received: by 10.141.13.6 with SMTP id q6mr3794686rvi.196.1271956895778; Thu, 22 Apr 2010 10:21:35 -0700 (PDT) Message-ID: Subject: Re: Jmeter Cookie problem From: Deepak Shetty To: JMeter Users List Content-Type: multipart/alternative; boundary=000e0cd112dcf147ed0484d68ad4 --000e0cd112dcf147ed0484d68ad4 Content-Type: text/plain; charset=ISO-8859-1 Ensure you have follow redirects instead of redirect automatically. Using View Results tree check whether the cookie gets set and whether JMeter is passing it back On Wed, Apr 21, 2010 at 11:46 PM, Anamika aaa wrote: > Hi , > > I am trying to test a web application using HTTPS on JMeter. I am using > JMeter 2-2. My test consists of the following: Get the login page, post > login form parameters, get the enter page. I have recorded the script using > Badboy by giving all the login details. > > When I switch to HTTPS on 443, I am redirected to the login page on the > second and third requests. I do not see the cookie information in the > request tab in the results tree and i am getting HTTP authorisation message > not validated error I believe that the Cookie Manager is not passing the > cookie information back with each subsequent request. > I have looked through the Users Guide, FAQ, and Bug list for any > information > about the Cookie Manager handling HTTPS request but have not found > anything. > Has anyone experienced this behavior using HTTPS in JMeter? > > > Regards > --000e0cd112dcf147ed0484d68ad4--