Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 40800 invoked from network); 9 Mar 2007 10:21:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Mar 2007 10:21:55 -0000 Received: (qmail 32970 invoked by uid 500); 9 Mar 2007 10:21:56 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 32258 invoked by uid 500); 9 Mar 2007 10:21:55 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 32247 invoked by uid 99); 9 Mar 2007 10:21:55 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Mar 2007 02:21:55 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of Brecht.Yperman@invenso.com designates 212.100.175.222 as permitted sender) Received: from [212.100.175.222] (HELO HPSERVER1.office.invenso.com) (212.100.175.222) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Mar 2007 02:21:44 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C76234.5DEEDAAE" Subject: RE: ntlm authentication and Axis 2 Date: Fri, 9 Mar 2007 11:19:15 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ntlm authentication and Axis 2 Thread-Index: AcdiMj889vTBID5QQJCpwbM24YFa6wAAX4sg References: From: "Brecht Yperman" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C76234.5DEEDAAE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, =20 I'm having a similar problem, where we are sending over 1000 calls in about one hour. However, for each call: - first a simple request is done - the proxy server responds that needs NTLM - then a request is sent with the proxyhost and the proxyport - the proxy server then responds that we don't have access to that URL - then a request is sent with all of the proxy parameters (host, port, user, domain, password) =20 Is it possible to get Axis2 to send all of the parameters the first time? This would reduce sending time with at least one second, I think (so over 25%). =20 Thanks, Brecht =20 From: Arindam Roy [mailto:arin_bec@hotmail.com]=20 Sent: vrijdag 9 maart 2007 11:05 To: axis-user@ws.apache.org Subject: ntlm authentication and Axis 2 =20 Hi, =20 I am using Axis 2 to communicate with a server which has ntlm authentication. When I am invoking web service methods which do not involve any attachment, it is working fine. Using TCP packet capturing, I can even see the NTLM authentication happening via challenge/response handshaking. One problem that I see here is that for every method invocation the ntlm authentication is occuring which is a kind of redundancy. I think this is happening because pre-authentication feature is not built into Axis 2 or common httpclient.=20 =20 ------_=_NextPart_001_01C76234.5DEEDAAE Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 

I'm having a similar problem, where we are sending over = 1000 calls in about one hour.

However, for each call:

- first a simple request is done

- the proxy server responds that needs = NTLM

- then a request is sent with the proxyhost and the = proxyport

- the proxy server then responds that we don't have = access to that URL

- then a request is sent with all of the proxy parameters = (host, port, user, domain, password)

 

Is it possible to get Axis2 to send all of the parameters = the first time? This would reduce sending time with at least one second, I = think (so over 25%).

 

Thanks,

Brecht

 

From:= Arindam = Roy [mailto:arin_bec@hotmail.com]
Sent: vrijdag 9 maart 2007 11:05
To: axis-user@ws.apache.org
Subject: ntlm authentication and Axis 2

 

Hi,
 
I am using Axis 2 to communicate with a server which has ntlm = authentication. When I am invoking web service methods which do not involve any = attachment, it is working fine. Using TCP packet capturing, I can even see the NTLM authentication happening via challenge/response handshaking. One problem = that I see here is that for every method invocation the ntlm authentication is occuring which is a kind of redundancy. I think this is happening = because pre-authentication feature is not built into Axis 2 or common = httpclient.

 <= /o:p>

------_=_NextPart_001_01C76234.5DEEDAAE--