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 0E6F8DDBD for ; Thu, 29 Nov 2012 22:33:07 +0000 (UTC) Received: (qmail 43841 invoked by uid 500); 29 Nov 2012 22:33:06 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 43815 invoked by uid 500); 29 Nov 2012 22:33:06 -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 43805 invoked by uid 99); 29 Nov 2012 22:33:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Nov 2012 22:33:06 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [209.65.160.86] (HELO nbfkord-smmo04.seg.att.com) (209.65.160.86) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Nov 2012 22:32:56 +0000 Received: from unknown [144.160.112.28] (EHLO tlpi048.enaf.dadc.sbc.com) by nbfkord-smmo04.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 282e7b05.0.1406134.00-492.3957811.nbfkord-smmo04.seg.att.com (envelope-from ); Thu, 29 Nov 2012 22:32:35 +0000 (UTC) X-MXL-Hash: 50b7e28367d2ce7f-07291126404be59a73409121dd307768889c2625 Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1]) by tlpi048.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id qATMWYcJ007433 for ; Thu, 29 Nov 2012 16:32:34 -0600 Received: from dalint02.pst.cso.att.com (dalint02.pst.cso.att.com [135.31.133.160]) by tlpi048.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id qATMWSet007159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 29 Nov 2012 16:32:29 -0600 Received: from MOSTLS1MSGHUB9B.ITServices.sbc.com (mostls1msghub9b.itservices.sbc.com [135.153.216.40]) by dalint02.pst.cso.att.com (RSA Interceptor) for ; Thu, 29 Nov 2012 16:31:56 -0600 Received: from MOSTLS1MSGUSR9J.ITServices.sbc.com ([135.153.216.19]) by MOSTLS1MSGHUB9B.ITServices.sbc.com ([135.153.216.40]) with mapi id 14.02.0318.001; Thu, 29 Nov 2012 16:31:56 -0600 From: "HUSSEY, SCOTT T" To: JMeter Users List Subject: RE: Strange behavior when performing basic authentication Thread-Topic: Strange behavior when performing basic authentication Thread-Index: AQHNzoD5PyO5s6Ylp0yRWgHJny1St5gBZU5A Date: Thu, 29 Nov 2012 22:31:56 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.215.10.52] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-RSA-Inspected: yes X-RSA-Classifications: public X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-SOURCE-IP: [144.160.112.28] X-AnalysisOut: [v=2.0 cv=cNhXRCiN c=1 sm=0 a=srMsL6ituuWTYeky9Bs9mA==:17 a] X-AnalysisOut: [=OA15bDmjXhkA:10 a=SMSVSR2FkCMA:10 a=ofMgfj31e3cA:10 a=BLc] X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R] X-AnalysisOut: [AAAA:8 a=9WVJWBecQPcA:10 a=pGLkceISAAAA:8 a=mV9VRH-2AAAA:8] X-AnalysisOut: [ a=8jX5ydJwH9tWSc89FZgA:9 a=CjuIK1q_8ugA:10 a=MSl-tDqOz04A] X-AnalysisOut: [:10] X-Virus-Checked: Checked by ClamAV on apache.org I've found HTTPClient 4 to be the best for NTLM authentication. I have seen= issues where I recorded using the Java implementation w/ the proxy server = and then switched to HTTPClient4 for playback w/ the best results. > -----Original Message----- > From: Fergal Hanley [mailto:fergalhanley@gmail.com] > Sent: Thursday, November 29, 2012 4:29 PM > To: user@jmeter.apache.org > Subject: Strange behavior when performing basic authentication >=20 > I'm getting some strange behavior when attempting to use JMeter to > perform > basic authentication against a web application. >=20 > I'm using the Authorization Manager for NTLM authentication. When I > attempt > to play back my script I get a 401 Unauthorized error response. I'f I fir= e > up the JMeter proxy server and record a snippet of script from the very > server I'm attempting to hit in my test, and then I play back the script > after this, it can authenticate. Does the fact that record change somethi= ng > in JMeter to make authorization work? This effect is retained as long as = I > keep the JMeter application open but lost when I close and reopen the too= l. >=20 > Other details about the test plan: >=20 >=20 > 1. I'm using Java implementation calls, HttpClient 3.1 and 4 never wor= ked > 2. Calls are being made through an internet proxy that I've configured > in jmeter.properties > 3. The application I'm targeting is a SharePoint site > 4. I'm using the HTTP Authorization Manager for server authentication > 5. I left the JMeter application open over night in a state where it w= as > able to play back the requests. When I came in the next day it was sti= ll > able to play back the requests but when I restarted the application it= was > once again unable to make the requests. >=20 >=20 > Any help would be greatly appreciated, >=20 > Thank you, > Fergal --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org For additional commands, e-mail: user-help@jmeter.apache.org