[ 
https://issues.apache.org/jira/browse/IVY-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kelly Schoenhofen closed IVY-1402.
----------------------------------

    Resolution: Duplicate

I see that my issues really are a duplicate of IVY-1336; using 2.3.0 release & 
commons-httpclient-3.0.jar, bad credentials (but a proper host & realm) put you 
in an endless loop. Ant -debug does not show anything going on, I had to see 
the loop in the Nexus log. Control-C broke me out with the following: 
^CJan 31, 2013 10:07:21 AM org.apache.commons.httpclient.HttpConnection 
releaseConnection
WARNING: HttpConnectionManager is null.  Connection cannot be released.

I am closing IVY-1402, as IVY-1336 is what I need fixed. 
                
> http authentication is disabled
> -------------------------------
>
>                 Key: IVY-1402
>                 URL: https://issues.apache.org/jira/browse/IVY-1402
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.3.0
>         Environment: Ubuntu 12.10, Ant 1.8.2, Ivy 2.3.0 release. 
>            Reporter: Kelly Schoenhofen
>              Labels: httpclient, newbie, nexus
>
> When I try to publish to a Sonatype Nexus server, with <credentials/> fully 
> populated, according to the Nexus debug logs, the header was empty, so it 
> goes with anonymous. According to ant -debug, at the end of the deliver block:
> Jan 31, 2013 9:41:36 AM org.apache.commons.httpclient.HttpMethodDirector 
> isAuthenticationNeeded
> INFO: Authentication requested but doAuthentication is disabled
> Why is doAuthentication disabled? How can I enable it? I have all the 2.3.0 
> dependencies in the lib folder of the project, so it uses its 
> commons-httpclient-3.0.jar rather then the jdk (which doesn't support http 
> auth, apparently?)
> Until I put commons-httpclient-3.0.jar into its lib/classpath folder, it 
> wasn't even trying. Now it says requested but doAuthentication is disabled. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to