archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Lamandé" <>
Subject Network Proxies - use full wagon http instead of lightweight
Date Sun, 02 Dec 2007 17:34:02 GMT
Hi to the developement team,

I've tried using Archiva inside an enterprise network. But I got a problem
to pass through a HTTP proxy with user authentication.
So I configured a network proxy (a lot of times ;-) ) but no results. The
proxy configuration seemed to be never used.

Finally, to resolve this problem, I needed to replace the dependency (in
archiva webapp) "*wagon-http-lightweight-1.0-beta-2*" by the more powerful "

This one makes use of common-http-client that provides full configuration of
network http proxy instead of the "native" environment properties
Now the network connections work gracefully with http proxy with or without
user authentication.

Could you consider replacing those dependencies in archiva, the way I've
done ?
I think that I won't be the only one to have the problem.

So I wil go on using the archiva repository. In my team, we were using
maven-proxy, and were looking for a much advanced one for a while. Thx to


P.S. : in the META-INF/plexus/components.xml of the
wagon-http-lightweight-1.0-beta-2, I think there is an error for the
"implementation" value of the "role-hint" *https* :
should be
instead of

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message