From ec38b22130344f77e4d8054695d331db84f1884c Mon Sep 17 00:00:00 2001 From: Brett Porter Date: Thu, 3 Apr 2008 11:59:54 +0000 Subject: [PATCH] [MRM-159] documentation for error handling git-svn-id: https://svn.apache.org/repos/asf/archiva/branches@644275 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/site/apt/adminguide/proxy-connectors.apt | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/archiva-1.0.x/archiva-docs/src/site/apt/adminguide/proxy-connectors.apt b/archiva-1.0.x/archiva-docs/src/site/apt/adminguide/proxy-connectors.apt index cf4dd72a3..5737091be 100644 --- a/archiva-1.0.x/archiva-docs/src/site/apt/adminguide/proxy-connectors.apt +++ b/archiva-1.0.x/archiva-docs/src/site/apt/adminguide/proxy-connectors.apt @@ -29,14 +29,18 @@ Understanding Proxy Connector Configuration of Apache Archiva By default, Archiva comes with the following policies: - * <<>> - how to behave for released artifact metadata (those not carrying a <<>> version). This can be set to <<>> (default), <<>>, <<>>, <<>> and <<>>. + * <<>> - how to behave for released artifact metadata (those not carrying a <<>> version). This can be set to <<>> (default), <<>>, <<>>, <<>> and <<>>. - * <<>> - how to behave for snapshot artifact metadata (those carrying a <<>> version). This can be set to <<>> (default), <<>>, <<>>, <<>> and <<>>. + * <<>> - how to behave for snapshot artifact metadata (those carrying a <<>> version). This can be set to <<>> (default), <<>>, <<>>, <<>> and <<>>. - * <<>> - how to handle incorrect checksums when downloading an artifact from the remote repository (ie, the checksum of the artifact does not match the corresponding detached checksum file). + * <<>> - how to handle incorrect checksums when downloading an artifact from the remote repository (ie, the checksum of the artifact does not match the corresponding detached checksum file). The options are to fail the request for the remote artifact, fix the checksum on the fly (default), or simply ignore the incorrect checksum - * <<>> - whether failures retrieving the remote artifact should be cached (to save network bandwidth for missing or bad artifacts), or uncached (default). + * <<>> - whether failures retrieving the remote artifact should be cached (to save network bandwidth for missing or bad artifacts), or uncached (default). + + * <<>> - if a remote proxy causes an error, this option determines whether an existing artifact should be returned (error when <<>>), or the error passed on regardless (<<>>). + + * <<>> - if a remote error is encountered, <<>> causes the error to be returned immediately, <<>> will return all errors after checking for other successful remote repositories first, and <<>> will disregard ay errors. [] -- 2.39.5