Return-Path: Delivered-To: apmail-maven-archiva-dev-archive@locus.apache.org Received: (qmail 78606 invoked from network); 31 Mar 2008 01:46:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Mar 2008 01:46:14 -0000 Received: (qmail 94501 invoked by uid 500); 31 Mar 2008 01:46:13 -0000 Delivered-To: apmail-maven-archiva-dev-archive@maven.apache.org Received: (qmail 94451 invoked by uid 500); 31 Mar 2008 01:46:13 -0000 Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: archiva-dev@maven.apache.org Delivered-To: mailing list archiva-dev@maven.apache.org Received: (qmail 94442 invoked by uid 99); 31 Mar 2008 01:46:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Mar 2008 18:46:13 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [69.36.241.87] (HELO mail.sventech.com) (69.36.241.87) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2008 01:45:20 +0000 Received: from mail.sventech.com (localhost.localdomain [127.0.0.1]) by mail.sventech.com (Postfix) with ESMTP id 81F0748051 for ; Sun, 30 Mar 2008 18:45:38 -0700 (PDT) Received: from [192.168.1.118] (ip72-208-56-187.ph.ph.cox.net [72.208.56.187]) by mail.sventech.com (Postfix) with ESMTP id 5FBEE4804F for ; Sun, 30 Mar 2008 18:45:38 -0700 (PDT) Message-ID: <47F04241.9010108@erdfelt.com> Date: Sun, 30 Mar 2008 18:45:37 -0700 From: Joakim Erdfelt User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080227 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: archiva-dev@maven.apache.org Subject: Re: plan for MRM-159 References: <7B5A1B53-ABC1-40ED-B1D6-418794B410D6@apache.org> In-Reply-To: <7B5A1B53-ABC1-40ED-B1D6-418794B410D6@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Checked: Checked by ClamAV on apache.org Heh, I can't grasp the nuances between Error handlings and update error handling. The proxy connector has a few places an exception could occur. (off the top of my head) * Request for remote content results in hostname (dns) exception. * Request for remote content results in auth exception. * Request for remote content results in connection exception. * Downloading the remote content fails midstream. (partial download) * Can't create directory for remote content to download into * Can't create file for remote content to download into (this is a temp file name, btw) * Can't rename remote content (temp filename) to actual name. * The client requesting the content has closed the connection early (no propogation issue here) * Network proxy error. * Exception while updating maven-metadata.xml file. * Failed policy (checksum, and in the future, the pgp check) - Joakim Brett Porter wrote: > Hi, > > For MRM-159 (should not respond with a 404 if proxying a file results > in a remote error), I intend to add two options to the proxy connector: > * Error handling: propagate immediately, propagate at end if not > successful (default), ignore > * Update error handling: propagate always, propagate if artifact not > present (default) > > Please tell me now if these aren't descriptive enough, firstly :) > > For the one that propagates at the end, I'll look into a way to list > all the errors that occurred in the response. > > WDYT? > > Cheers, > Brett > > -- > Brett Porter > brett@apache.org > http://blogs.exist.com/bporter/ >