[
http://jira.codehaus.org/browse/MRM-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142486#action_142486
]
Olaf Fricke commented on MRM-631:
---------------------------------
I have fought against the same problem last week and finally found a solution.
We have the same setup as described above in our company: we have a local
maven2 repository that is used as server for our own artifacts. This repository
needs to be reached directly. In addition, we are using a couple of remote
repositories in the internet. To reach these repositories, a network proxy has
to be used.
We are using archiva 1.0.2 as mirror in the maven configuration to proxy all
these repositories. Everything works fine, as long as we are using either the
local repository without a proxy only or the remote repositories behind the
network proxy. Using both kinds of repositories results in strange error
messages.
After hours of testing, researching and even code reviews I found the problem:
as soon as a network proxy is defined on the archiva configuration page, saving
a proxy connector the used direct connection via the archiva configuration
changes the archiva.xml configuration file. Instead of the usual empty
<proxyId/> tag, the configuration file contains <proxyId>(direct
connection)</proxyId>. And this does not work.
After I have removed the the '(direct connection)' manually from the
configuration file the mixed setup is working!
> network proxy is always used when defined
> -----------------------------------------
>
> Key: MRM-631
> URL: http://jira.codehaus.org/browse/MRM-631
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.0
> Environment: Linux and Windows with JRE 1.5
> Reporter: Jacques REYNARD
> Assignee: Brett Porter
> Fix For: 1.1.x
>
> Attachments: archiva.xml
>
>
> I've installed Archiva 1.0 as a Maven proxy repository for internet and
> corporate repositories.
> I've added the remote Internet Repositories, the network proxy and the proxy
> connectors.
> It works well for the internet repositories but when Archiva tries to connect
> to the corporate repository in the same subnetwork, Archiva uses
> the network proxy despite the proxy connector is set to Direct Connection.
> If no proxy connectors is defined, Archiva didn't try to get data form the
> corporate repository.
> If no network proxy is defined, Archiva can contact the corporate repository
> but not the Internet ones.
> I've done a test with network capture (wireshark ex ethereal) to confirm the
> network proxy defined is used. And the result confirm my opinion, the proxy
> is used.
> I attach the archiva.xml configuration file in order to check it.
> The corporate repository is localrepo and is available in http form the
> archiva server using lynx, wget and telnet.
> Thanks for your help
--
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
