From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: encourage switch away from heanet.sf.net
Date: Sat, 09 Dec 2006 11:35:36 +0100 [thread overview]
Message-ID: <ele3hp$u6v$1@sea.gmane.org> (raw)
In-Reply-To: <63497983.20061208141958@vanille-media.de>
Michael 'Mickey' Lauer wrote:
>> Instead they automatically 302 you now.
>
> If that's true, then +1 from me.
It seems they do. And a sample session I wanted to provide as proof
apparently also revealed how they deal with the situation that a mirror
does not have the file. I post only the relevant lines here.
$ wget http://downloads.sf.net/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk
HTTP Anforderung gesendet, warte auf Antwort... 302 Found
Platz:
http://downloads.sourceforge.net/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk
HTTP Anforderung gesendet, warte auf Antwort... 302 Found
Platz:
http://ovh.dl.sourceforge.net/sourceforge/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk
HTTP Anforderung gesendet, warte auf Antwort... 200 OK
302 twice, then 200 from ovh. Download successful.
$ rm qpf-unismall-100_1.0.0-r0_all.ipk
$ wget http://downloads.sf.net/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk
HTTP Anforderung gesendet, warte auf Antwort... 302 Found
Platz:
http://downloads.sourceforge.net/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk
HTTP Anforderung gesendet, warte auf Antwort... 302 Found
Platz:
http://puzzle.dl.sourceforge.net/sourceforge/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk
HTTP Anforderung gesendet, warte auf Antwort... 302 Found
Platz:
http://prdownloads.sourceforge.net/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk?download&failedmirror=puzzle.dl.sourceforge.net
HTTP Anforderung gesendet, warte auf Antwort... 301 Moved Permanently
Platz:
http://downloads.sourceforge.net/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk?download&failedmirror=puzzle.dl.sourceforge.net
HTTP Anforderung gesendet, warte auf Antwort... 302 Found
Platz:
http://osdn.dl.sourceforge.net/sourceforge/gakusei/qpf-unismall-100_1.0.0-r0_all.ipk
HTTP Anforderung gesendet, warte auf Antwort... 200 OK
302 twice to puzzle which does not have the file and thus 302's again to
prdownloads. There is an added attribute that this file failed for the
mirror and I assume that downloads.sf.net will act on that information
for future downloads. prdownloads sets a 301, we get another 302 and
then osdn answers the request. In some cases quite a few hops but it
seems to work.
Out of curiousity, I tested out what happens with files that are not on
the sf.net network. It seems that one of two things happens. If heanet
is the first mirror being redirected to and it cannot find the file, it
will answer with a 404 itself. Otherwise, if some other mirror is used
first, prdownloads will redirect to osdn which will redirect again to
prdownloads with &failedmirror=osdn.dl.sourceforge.net. A 404 is the
answer.
next prev parent reply other threads:[~2006-12-09 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 13:15 RFC: encourage switch away from heanet.sf.net Rolf Leggewie
2006-12-08 13:19 ` Michael 'Mickey' Lauer
2006-12-09 10:35 ` Rolf Leggewie [this message]
2006-12-10 22:30 ` Richard Purdie
2006-12-11 20:44 ` Marcin Juszkiewicz
2006-12-12 12:14 ` Rolf Leggewie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ele3hp$u6v$1@sea.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.