Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 64159 invoked from network); 22 Apr 2010 06:46:30 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Apr 2010 06:46:30 -0000 Received: (qmail 63877 invoked by uid 500); 22 Apr 2010 06:46:29 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 63728 invoked by uid 500); 22 Apr 2010 06:46:28 -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 63713 invoked by uid 99); 22 Apr 2010 06:46:28 -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 06:46:28 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anamikaqtp@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-wy0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Apr 2010 06:46:21 +0000 Received: by wyb35 with SMTP id 35so314990wyb.31 for ; Wed, 21 Apr 2010 23:46:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:received:message-id :subject:from:to:content-type; bh=Un4GDT8fQ5ITsey2QDkJspo9iQzikb8idIllloIlTHA=; b=OxRH/s/SaQBRnf1z5xNnJOg+Av6WmSXQ/LGik8gYY6/Kx4IOimqEeimgLhrvzSXHM3 ubew1pPhh3r0+x9FS5q1vajiXp4e4i5AXDW0/KLA5uJfi/zD9nHdMhhPZbaNtGYLIXIy qQa5FYMQW74sXJ7dUOBNbTLH7Xnco1TYFPt7g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ZPX8c4qShRBEuDNHpmphmfxMouofQTubOQIOCiY12UbgucqchmCvO0KW2j5DZolxQv HyB21b8wlcW6J9zhghSJhwE5YyKL5PX1ztZ5GoxlF/ni5FijafzBFznHuX1dxdBsq+8a JBUIaktfBRhJe3F2xwX7ml0B28GwrMPc1SVc0= MIME-Version: 1.0 Received: by 10.216.177.205 with HTTP; Wed, 21 Apr 2010 23:46:00 -0700 (PDT) Date: Thu, 22 Apr 2010 12:16:00 +0530 Received: by 10.216.154.7 with SMTP id g7mr5205044wek.7.1271918760184; Wed, 21 Apr 2010 23:46:00 -0700 (PDT) Message-ID: Subject: Jmeter Cookie problem From: Anamika aaa To: JMeter Users List Content-Type: multipart/alternative; boundary=0016e64c2de4e24ce00484cda98e --0016e64c2de4e24ce00484cda98e Content-Type: text/plain; charset=ISO-8859-1 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 --0016e64c2de4e24ce00484cda98e--