------ Understanding Network Proxy Configuration of Apache Archiva ------ ~~ Licensed to the Apache Software Foundation (ASF) under one ~~ or more contributor license agreements. See the NOTICE file ~~ distributed with this work for additional information ~~ regarding copyright ownership. The ASF licenses this file ~~ to you under the Apache License, Version 2.0 (the ~~ "License"); you may not use this file except in compliance ~~ with the License. You may obtain a copy of the License at ~~ ~~ http://www.apache.org/licenses/LICENSE-2.0 ~~ ~~ Unless required by applicable law or agreed to in writing, ~~ software distributed under the License is distributed on an ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~~ KIND, either express or implied. See the License for the ~~ specific language governing permissions and limitations ~~ under the License. Understanding Network Proxy Configuration of Apache Archiva Archiva uses the terminology "proxy" for two different concepts: * The remote repository proxying cache, as configured through {{{./proxy-connectors.html} proxy connectors}} between repositories * Network proxies, which are traditional protocol based proxies (primarily for HTTP access to remote repositories over a firewall) [] Network proxies are configured using standard HTTP proxy settings as provided by your network administrator. Once configured, the network proxy can be attached to operations that access remote resources. At present, this is configured on the remote repository proxy connectors that need to access the remote repository over the HTTP protocol. * Network Proxy Settings and the JVM As Archiva still targets Java 5 and uses the built-in networking libraries, it must configure these settings using system properties. This can be problematic in two scenarios: * if you use multiple different network proxies on different proxy connectors, they may clash * if you deploy other applications into the same container as Archiva, they will likely pick up the settings [] Please refer to {{{http://jira.codehaus.org/browse/MRM-1248} MRM-1248}} for workarounds and to track the issue. ~~TODO: walkthrough configuration