[
http://jira.codehaus.org/browse/WAGON-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved WAGONHTTP-14 to WAGON-116:
---------------------------------------------
Affects Version/s: (was: 1.0-beta-1)
(was: 1.0-alpha-6)
Fix Version/s: (was: 1.x)
1.x
Key: WAGON-116 (was: WAGONHTTP-14)
Project: Maven Wagon (was: wagon-http)
> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>
> Key: WAGON-116
> URL: http://jira.codehaus.org/browse/WAGON-116
> Project: Maven Wagon
> Issue Type: Bug
> Environment: Linux with BlueCoat firewall/proxy
> Reporter: Mykel Alvis
> Fix For: 1.x
>
> Attachments: myfile.txt
>
>
> On a windows machine, authenticated on an NT domain, the proxy username and
> password appear to be sufficient for getting the lightweight http wagon to
> download artifacts.
> On a linux machine, which is connected to the domain's network but not
> authenticated on the domain, the same settings do not work.
> To further compound the confusion of the situation,
> setting http_proxy with the specified username and password using
> export http_proxy=http://USERNAME:[EMAIL PROTECTED]:PROXYPORT
> allows me to use wget on an artifact's URL and retrieve it from the command
> line, indicating an issue with the proxy settings for java (since a compiled
> app from the command line successfully navigates the proxy).
> There appears to be no additional logging available.
> Attached is the output of mvn -X that shows the trace.
> Currently checking out the trunk sources to attempt further debugging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
