maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mykel Alvis (JIRA)" <>
Subject [jira] Commented: (WAGON-116) Proxy authentication not authenticating with settings
Date Fri, 16 May 2008 14:01:27 GMT


Mykel Alvis commented on WAGON-116:

Yes.  The USERNAME in the above example required that. 
You can also do it by 
export HTTP_PROXY='http://DOMAIN\USER:PW@proxy:PORT'
or export HTTP_PROXY="http://DOMAIN\\USER:PW@proxy:PORT"

First one appears more generic across shells (except for "export", of course)

It would maybe be nice if there were a parameter to set for this in the provider, rather than
having to juggle escaped backslashes for windows, but that's just an idea.

> Proxy authentication not authenticating with settings
> -----------------------------------------------------
>                 Key: WAGON-116
>                 URL:
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>         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:PASSWORD@PROXYIP: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:
For more information on JIRA, see:


View raw message