[
http://jira.codehaus.org/browse/MRM-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142487#action_142487 ]
Olaf Fricke commented on MRM-254:
---------------------------------
Please have a look at my comment to MRM-631, this may solve your problem as well.
> connecting proxied repositories without http-proxy fails
> --------------------------------------------------------
>
> Key: MRM-254
> URL:
http://jira.codehaus.org/browse/MRM-254> Project: Archiva
> Issue Type: Improvement
> Components: remote proxy
> Environment: archiva-trunk on SuSE-Linux in intranet-environment behind a firewall and with http-proxy
> Reporter: Stefan Hübner
> Assignee: Fabrice BELLINGARD
> Priority: Critical
> Fix For: 1.0-alpha-2
>
>
> If one configures Archiva to proxy another inhouse repository, Archiva struggles to connect to the proxied repository. The log file contains 503 HTTP Error Codes for any attempt to connect to the second repo. This is because Archiva tries to connect to the second server via http-proxy-connection (even though the proxied repository is configured not to connect through http-proxy).
> First thing, the "Use HTTP Proxy" option doesn't work properly since Archiva *does* open proxy-connections even with that option inactive.
> Second: I figured out, that there's a hidden option for HTTP-Proxy, only configurable in Archiva's archiva.xml file. If the proxy-element contains a "nonProxyHosts"-element (same as in maven settings.xml) and that element lists the second server, all 503 return codes vanish.
> Conclusion: either the "Use HTTP proxy"-option is screwed or serves a different purpose. If first, please fix that issue. If second, please make "nonProxyHosts" configurable via UI.
> Cheers,
> Stefan
--
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
