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 2B024678B for ; Thu, 26 May 2011 17:22:03 +0000 (UTC) Received: (qmail 50578 invoked by uid 500); 26 May 2011 17:22:02 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 50546 invoked by uid 500); 26 May 2011 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 50537 invoked by uid 99); 26 May 2011 17:22:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2011 17:22:02 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shettyd@gmail.com designates 209.85.218.44 as permitted sender) Received: from [209.85.218.44] (HELO mail-yi0-f44.google.com) (209.85.218.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2011 17:21:55 +0000 Received: by yic13 with SMTP id 13so524031yic.31 for ; Thu, 26 May 2011 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:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=fcX2mcfixRxgK2+tOjMwzKbpmm08kOskM4lZxzlQkEw=; b=PcyWa2DXBZ2k1p7BnE5M2LBpqw+2pnkILYjHDVrzUmwh1bPMilbTRWQQsm2Hns9u5F yaEaoQq6xwqeqO3sKwn0v8fLyTmSRGtzVw+45I6KCZ6hJeQafcCYV23enURpjKO85rTs bbl29q/zz4ShhR00F3+qfFgEpAR4iCE+rlSxY= 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=kHdT6KcnJwwpSRvzwx+th37Suj789zHD1I10AuHATTZjOvHDh/UjyNzBI2pJoR4FL6 yz1CpCZMtnWBgallG/pW8oEgm5SX8jZAN5ZOgRcJPVHrS4IDwXaeGSCCbOgpJdHAq1fN HG7z11l/AL0G1/AN7IVxFg9Uo4tt/POzLpQWY= MIME-Version: 1.0 Received: by 10.151.76.13 with SMTP id d13mr1087692ybl.444.1306430494902; Thu, 26 May 2011 10:21:34 -0700 (PDT) Received: by 10.151.148.12 with HTTP; Thu, 26 May 2011 10:21:34 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 May 2011 10:21:34 -0700 Message-ID: Subject: Re: JSON Request- Urgent help From: Deepak Shetty To: JMeter Users List Content-Type: multipart/alternative; boundary=000e0cd70d7c928bc004a4310d5f X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd70d7c928bc004a4310d5f Content-Type: text/plain; charset=ISO-8859-1 Hi if you could do this , it wouldnt be a very good captcha would it? the purpose of a captcha is to prevent automated bots from submitting forms . The only way around this problem is to change the server side application . A configuration flag or something is used in the environment or request to indicate to your app to either bypass captcha checking or the previous request also returns the value of the captcha that is to be entered regards deepak On Thu, May 26, 2011 at 3:51 AM, Ragini Thakur wrote: > Hi all, > > In the application under test a JSON request is sent and in its response > server sends back an image. The image has verification code which is to be > used to next login request. > > How can we extract the image text /verification code imprinted to be sent > to the next request. > > TG > > Get Request - LoginPage.do > GET - Captcha.json > In response we get image which has verification code > POST - Login.json [ Parameters : User Name, password, verification code = > to be used from image response received from previous request ] > > Regards, > Ragini Thakur > > > > "Legal Disclaimer: This electronic message and all contents contain > information from Cybage Software Private Limited which may be privileged, > confidential, or otherwise protected from disclosure. The information is > intended to be for the addressee(s) only. If you are not an addressee, any > disclosure, copy, distribution, or use of the contents of this message is > strictly prohibited. If you have received this electronic message in error > please notify the sender by reply e-mail to and destroy the original message > and all copies. Cybage has taken every reasonable precaution to minimize the > risk of malicious content in the mail, but is not liable for any damage you > may sustain as a result of any malicious content in this e-mail. You should > carry out your own malicious content checks before opening the e-mail or > attachment." > www.cybage.com > > --000e0cd70d7c928bc004a4310d5f--