Return-Path: X-Original-To: apmail-jmeter-user-archive@www.apache.org Delivered-To: apmail-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 0F0D29BAF for ; Mon, 12 Mar 2012 11:33:18 +0000 (UTC) Received: (qmail 10651 invoked by uid 500); 12 Mar 2012 11:33:17 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 10613 invoked by uid 500); 12 Mar 2012 11:33:17 -0000 Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JMeter Users List" Delivered-To: mailing list user@jmeter.apache.org Received: (qmail 10604 invoked by uid 99); 12 Mar 2012 11:33:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2012 11:33:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of philippe.mouawad@gmail.com designates 209.85.210.171 as permitted sender) Received: from [209.85.210.171] (HELO mail-iy0-f171.google.com) (209.85.210.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2012 11:33:12 +0000 Received: by iadj38 with SMTP id j38so7789078iad.2 for ; Mon, 12 Mar 2012 04:32:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2cK56yK/uin1mdRqohPkEOC5nxovreaRIIpFyOsfB2w=; b=YNi3HseAGa4QBJ9h+b2HyOf4VqLWGdZy0XWWQy3y4ng3zDq+pW9OjidhmYYogYQXZo DfaagX0PPpDzBsW3jWiBwDZR6ZGGAtZi1Zmsf92fuRJV3M3xD9cl9m4zV662QYwKvr3t T93p1glCBMvLVpgVAD9+YMpGZzzP2X72E4eEF3Kw5V8YrvQyP1wPItd/sLH9BYL8PxRy l8sNqiXsIgehAAOEmvf9BMPbCyNIpe6NKVfB+pw6/RkoEkZ6R7gBnmHAQ6HUvSfR/tgO UG/T7rtTK4/17u4UTkl8+OgIvfRBE7wB6nDoc8YAwkKJ5mj4GlOj+ukU1kcOtfF/9R6T ctdA== MIME-Version: 1.0 Received: by 10.50.47.232 with SMTP id g8mr2857292ign.18.1331551971611; Mon, 12 Mar 2012 04:32:51 -0700 (PDT) Received: by 10.231.101.69 with HTTP; Mon, 12 Mar 2012 04:32:51 -0700 (PDT) In-Reply-To: <00c401cd0034$19f70190$4de504b0$@yahoo.com> References: <00b101cd0027$3eed5c40$bcc814c0$@yahoo.com> <00c401cd0034$19f70190$4de504b0$@yahoo.com> Date: Mon, 12 Mar 2012 12:32:51 +0100 Message-ID: Subject: Re: Recording proxy truncates cookie names. Bug? From: Philippe Mouawad To: JMeter Users List Content-Type: multipart/alternative; boundary=14dae93406c744943304bb0a1ab0 X-Virus-Checked: Checked by ClamAV on apache.org --14dae93406c744943304bb0a1ab0 Content-Type: text/plain; charset=ISO-8859-1 Hello, There was indeed a bug even if spoofing was not active. Issues : - https://issues.apache.org/bugzilla/show_bug.cgi?id=52886 - https://issues.apache.org/bugzilla/show_bug.cgi?id=52885 Are now fixed in r1299631. You can get nightly build to test here: - http://jmeter.apache.org/nightly.html Regards Philippe M. http://www.ubik-ingenierie.com On Mon, Mar 12, 2012 at 10:40 AM, David Parks wrote: > Thanks for the fast response! > > I don't have HTTPS spoofing checked on the JMeter Proxy, nor anything in > the > 'Only spoof URLs maching:' field. > > Can you explain more about where you're going with this thought? > > Thanks, > Dave > > > -----Original Message----- > From: Philippe Mouawad [mailto:philippe.mouawad@gmail.com] > Sent: Monday, March 12, 2012 3:28 PM > To: JMeter Users List > Subject: Re: Recording proxy truncates cookie names. Bug? > > Hello, > This is related to HTTPS spoofing. > > Since 2.4 it's better not to use Spoofing when recording HTTPS traffic. > > Regards > Philippe M. > http://www.ubik-ingenierie.com > > On Mon, Mar 12, 2012 at 9:07 AM, David Parks > wrote: > > > When recording using the JMeter proxy (v2.6) against an https site we > > are seeing cookie names truncated in the browser. > > > > > > > > Specifically, all cookies that start with 'secure' get the word 'secure' > > truncated. > > > > > > > > Example: > > > > During recording, when the site sets a cookie named 'secure_token', > > the cookie that shows up in the browser is '_token' > > > > > > > > We tested this with another cookie 'secure_test_cookie', again, the > > browser ends up with a cookie called '_test_cookie'. Other cookie > > names seem unaffected. > > > > > > > > This only happens when recording through the JMeter proxy. Normal site > > operation stores the correct cookie name. > > > > > > > > Any thoughts from anyone on this weird behavior? > > > > > > > -- > Cordialement. > Philippe Mouawad. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org > For additional commands, e-mail: user-help@jmeter.apache.org > > -- Cordialement. Philippe Mouawad. --14dae93406c744943304bb0a1ab0--