Return-Path: X-Original-To: apmail-jakarta-jmeter-user-archive@www.apache.org Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 976DE83DB for ; Sun, 11 Sep 2011 20:35:27 +0000 (UTC) Received: (qmail 57176 invoked by uid 500); 11 Sep 2011 20:35:26 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 57122 invoked by uid 500); 11 Sep 2011 20:35:26 -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 57113 invoked by uid 99); 11 Sep 2011 20:35:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Sep 2011 20:35:26 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=FREEMAIL_FROM,SPF_SOFTFAIL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of oliver_lloyd@hotmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Sep 2011 20:35:21 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R2qk1-0000qn-4S for jmeter-user@jakarta.apache.org; Sun, 11 Sep 2011 13:35:01 -0700 Date: Sun, 11 Sep 2011 13:35:01 -0700 (PDT) From: Oliver Lloyd To: jmeter-user@jakarta.apache.org Message-ID: <1315773301130-4792359.post@n5.nabble.com> In-Reply-To: References: <1315169991959-4768360.post@n5.nabble.com> <1315647765773-4789171.post@n5.nabble.com> Subject: Re: HTTPS log-in problem gets rough MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit You could try coming at the problem from some different angles: 1. How does the application you are testing maintain state? 2. What is written to the server logs when the JMeter script is running? 3. Re. the json string. Is this the response that you get in a browser when you login? If yes, state is not maintained, if no, the login POST is wrong. ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/HTTPS-log-in-problem-gets-rough-tp4768159p4792359.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org