Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 95589 invoked from network); 27 Apr 2010 16:45:21 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Apr 2010 16:45:21 -0000 Received: (qmail 23197 invoked by uid 500); 27 Apr 2010 16:45:20 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 23157 invoked by uid 500); 27 Apr 2010 16:45:20 -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 23149 invoked by uid 99); 27 Apr 2010 16:45:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 16:45:20 +0000 X-ASF-Spam-Status: No, hits=1.6 required=10.0 tests=AWL,FREEMAIL_FROM,FREEMAIL_REPLY,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.222.182 as permitted sender) Received: from [209.85.222.182] (HELO mail-pz0-f182.google.com) (209.85.222.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 16:45:13 +0000 Received: by pzk12 with SMTP id 12so9599288pzk.32 for ; Tue, 27 Apr 2010 09:44:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=x3IPhIKoJA1IHwpvJWIBKI+N5mYhwPls1OyUe9cgKXI=; b=uw3dvA5xO+MQtOxXDAHqbDUou90RMhMMpaVvWGX8SwNzCzEUArFlD/7QmWag1ZlyB/ 1A8WlHYg436/rLDjgDj6BixhpJ1rgLGs8i7TcTWZspBbqcsN6D5bzG2gDpT8VpcmzxKR ZCw9mOEDPKB9u6UfZ54Vkir2R7qcBjGz4imjk= 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=KGy242dZktm8byKaTo/7TCc/p62tNs/uRx6uE9akbg186N3ZklItpNJTffEHNkthEx 6muT3dZLEeta0NwZMj0xh+hEoCSraC36m8XRmUuNBvqPibCbfQFR78LUq/A7KJ6J/8jy yftKzJZ3rjKC+ysFfDBhsbgJPGqHhc8GWbqS4= MIME-Version: 1.0 Received: by 10.141.214.26 with SMTP id r26mr6163220rvq.225.1272386692816; Tue, 27 Apr 2010 09:44:52 -0700 (PDT) Received: by 10.140.255.21 with HTTP; Tue, 27 Apr 2010 09:44:52 -0700 (PDT) In-Reply-To: References: Date: Tue, 27 Apr 2010 09:44:52 -0700 Message-ID: Subject: Re: Jmeter Cookie problem From: Deepak Shetty To: JMeter Users List Content-Type: multipart/alternative; boundary=000e0cd17992d7adc904853a9c7f --000e0cd17992d7adc904853a9c7f Content-Type: text/plain; charset=ISO-8859-1 1) JMeter does not support or execute javascript. However this is not necessarily a problem because some applications do display a noscript message (which is perhaps what you are seeing) and autosubmit the form with javascript(which you will do as a separate request in JMeter) 2) SAML parameter values are dynamic. If you have recorded and you replay the script it wont work. You must extract all the hidden values from the request (Assuming you use a POST profile.) On Mon, Apr 26, 2010 at 11:50 PM, Anamika aaa wrote: > Hi > > Thank u sebb for ur reply > I tried using Follow redirects but now i am facing a new prob along with > the > old one that says > > 1)Browser does not support JavaScript press continue to proceed in the > ViewTree Listener. I have enabled Javascript in both IE and Mozilla but its > still throwing the same error > > 2) The page that is throwing 401 unauthorised error also says SAML message > is not getting validated . It s a Single Sign On Page.The Cookie is now > getting set for the this page after the Follow Redirects s used.But the > error s still the same > Can anyone pleasetell me what the prob might be... > > Regards > > > On Mon, Apr 26, 2010 at 5:04 PM, sebb wrote: > > > On 26/04/2010, Anamika aaa wrote: > > > Thanks for all the replies .. > > > i am using 2.3.2 now but its the same problem.. > > > > The current version of JMeter is 2.3.4. > > > > > The follow redirects is > > > already selected since it is a bad boy script ... But the problem if i > > dont > > > tick the Automatically redirect checkbox my application throws a 302 > > > response code and doesnt go further . > > > > So long as you tick "follow redirects" JMeter should follow 302s. > > > > If it does not, please check the jmeter.log file for errors, and check > > the format of the 302 response in the Tree View Listener. > > > > > After giving the credentials for login the application though logs > in > > > successfully it is going back to the same login page instead of > > redirecting > > > to the application.. > > > > Some applications provide cookies as part of the redirect processing. > > These will not be seen by JMeter if you select "Automatically > > redirect". > > > > > Please let know if anyone has faced the same type of > > > problem.. > > > > Have you tried searching the mailing list for similar problems? > > > > > > > > Regards > > > > > > > > > > > > > > > On Thu, Apr 22, 2010 at 10:51 PM, Deepak Shetty > > wrote: > > > > > > > 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 > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org > > > > > --000e0cd17992d7adc904853a9c7f--