Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 23019 invoked from network); 22 Jan 2009 00:00:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jan 2009 00:00:43 -0000 Received: (qmail 81997 invoked by uid 500); 22 Jan 2009 00:00:41 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 81968 invoked by uid 500); 22 Jan 2009 00:00:41 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 81952 invoked by uid 99); 22 Jan 2009 00:00:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 16:00:41 -0800 X-ASF-Spam-Status: No, hits=4.0 required=10.0 tests=DNS_FROM_OPENWHOIS,FORGED_YAHOO_RCVD,NORMAL_HTTP_TO_IP,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2009 00:00:33 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LPmzU-0001xn-Sj for ivy-user@ant.apache.org; Wed, 21 Jan 2009 16:00:12 -0800 Message-ID: <21593688.post@talk.nabble.com> Date: Wed, 21 Jan 2009 16:00:12 -0800 (PST) From: CalvinJ To: ivy-user@ant.apache.org Subject: 2.0.0rc2 HTTP Authentication For Publishing Not Working MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: calvinxj1@yahoo.com X-Virus-Checked: Checked by ClamAV on apache.org I'm hoping some kind person can help answer my question in regards to Ivy and HTTP authentication when publishing. I'm using Ivy 2.0.0rc2. I believe I've followed all the instructions correctly, but I can't get HTTP authenication to work when publishing my artifacts. I sat the commons-httpclient3.1.jar on my classpath as instructed and verified it's on the Ant classpath by seeing the classpath setting in Ant debug mode: commons-httpclient-3.1.jar I've tried adding the _________________________________________________ ivysettings.xml And yet I get the following error: java.io.IOException: Access to URL http://100.23.20.7/artifactory/libs-snapshots/ com/mycompany/app/1.1.6-SNAPSHOT/app-1.1.6-SNAPSHOT.zip was refused by the server: Authentication is required. at org.apache.ivy.util.url.AbstractURLHandler.validatePutStatusCode(AbstractURLHandler.java:73) at org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:208) at org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatc Notice it's using the BasicURLHandler instead of the HttpClient one. When looking at the source code for URLHandlerRegistry, none of the verbose messages (e.g., jakarta commons httpclient) are printed out. Also, in Ant debug mode, my credentials look like they're being picked up by Ivy. I see the following printed out: credentials added: 100.23.20.7 calvin/******** credentials added: snapshots@100.23.20.7 calvin/******** Any help or suggestions would be appreciated. Thanks. -- View this message in context: http://www.nabble.com/2.0.0rc2-HTTP-Authentication-For-Publishing-Not-Working-tp21593688p21593688.html Sent from the ivy-user mailing list archive at Nabble.com.