Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 7803 invoked from network); 12 Sep 2009 08:53:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Sep 2009 08:53:13 -0000 Received: (qmail 9592 invoked by uid 500); 12 Sep 2009 08:53:13 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 9533 invoked by uid 500); 12 Sep 2009 08:53:13 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 9523 invoked by uid 99); 12 Sep 2009 08:53:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Sep 2009 08:53:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com designates 209.85.220.216 as permitted sender) Received: from [209.85.220.216] (HELO mail-fx0-f216.google.com) (209.85.220.216) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Sep 2009 08:53:02 +0000 Received: by fxm12 with SMTP id 12so1211549fxm.20 for ; Sat, 12 Sep 2009 01:52:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=0LPLCzYPs1RXiQ5g9xqIsm2/ww3VdjDhPrt6bcRTK4E=; b=pdL2mPed50lSuUB3QZf9rt5oGn6fK1tm8RSCrbsI+gnFwv/3O1hdlhv0r2mcMFkQm+ yz0wkJteae5QRPs3N3g8CosSkVyKbm+oph9HPGPD2A9HcohFp2omkH1yWco0jrL2AnVw zj/GWowc0xAaFxItk3vjGSEeVhaXE8NqHw67M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=nflWkVSV6nvMPbUtmSCwa/x+J9vmJlE0QnsD1BlrdZNIb4N9DBdO6ihLH2/XUkkqQK Dhh7IUJv/cQeHaAVCmTrGuUaebXQtR9+PSi7MKG12rUiFDzxVt8rcK8/aT8rpFxUccqq /n3AI1a7u9BjkJ5Fyw3nnK9bqtaDm+juxfEDA= MIME-Version: 1.0 Received: by 10.204.156.205 with SMTP id y13mr2950486bkw.116.1252745559191; Sat, 12 Sep 2009 01:52:39 -0700 (PDT) In-Reply-To: <25406191.post@talk.nabble.com> References: <25406191.post@talk.nabble.com> From: Claus Ibsen Date: Sat, 12 Sep 2009 10:52:19 +0200 Message-ID: <5380c69c0909120152k5a8faf9dh1b308da708075b2b@mail.gmail.com> Subject: Re: Broken Download Links for New Releases To: users@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Some of the other mirrors is working fine. So I guess its more of an Apache infrastructure problem, that the Camel release itself. On Fri, Sep 11, 2009 at 8:32 PM, Bob Pollack w= rote: > > The links for downloading Camel releases appear to be broken. For example= , if > I navigate to =A0http://camel.apache.org/camel-200-release.html Overview = > > Download > Camel 2.0.0 Release =A0and scroll to the bottom, the link for = the > Windows version points to > http://www.apache.org/dyn/closer.cgi/activemq/apache-camel/2.0.0/apache-c= amel-2.0.0.zip > http://www.apache.org/dyn/closer.cgi/activemq/apache-camel/2.0.0/apache-c= amel-2.0.0.zip > . When I click this link, the suggested mirror site link is > http://apache.siamwebhosting.com/activemq/apache-camel/2.0.0/apache-camel= -2.0.0.zip > http://apache.siamwebhosting.com/activemq/apache-camel/2.0.0/apache-camel= -2.0.0.zip > . But when I click this link, I get a 404 message. > > The actual release file appears to be at > http://apache.siamwebhosting.com/camel/apache-camel/2.0-M3/apache-camel-2= .0-M3-src.zip > http://apache.siamwebhosting.com/camel/apache-camel/2.0-M3/apache-camel-2= .0-M3-src.zip > . In other words, the top-level directory is camel/apache-camel, not > activemq/apache-camel. If I go to this root directory (that is, > http://apache.siamwebhosting.com/camel/apache-camel/ > http://apache.siamwebhosting.com/camel/apache-camel/ , I see a list of > subdirectories that seem to be every release from 1.6.0 up. > > I have seen this same pattern in a number of the mirrors (for obvious > reasons, I have not checked all of them). I believe that this is the prob= lem > reported > http://www.nabble.com/Camel-2.0---FTP-directory-problem-td24973778.html#a= 25063609 > elsewhere in this forum , in which a user has a problem that she could no= t > correct with a new release because she could not find the new release. > > Are these download links actually broken, or I am I doing something wrong= ? > Has anyone else experienced this problem (besides the one report cited > above)? > -- > View this message in context: http://www.nabble.com/Broken-Download-Links= -for-New-Releases-tp25406191p25406191.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > --=20 Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus