This is a test setup of the http-redirector project by
Raphael Geissert. It aims to solve the problem of choosing a Debian mirror
among the hundreds available, and other typical problems related to the
mirrors. The redirector takes into consideration the geo and network location
of the user and the mirror, the requirements of the user (such as the
architecture of the requested files, IP address family, etc.), and the
status of the mirrors (such as their availability and freshness.)
If you are familiar with cdn.debian.net you should think of
http.debian.net as a superior replacement.
Give the demonstration a try!
Replace your currently configured Debian mirror in sources.list with the following address:
http://http.debian.net/debiane.g.
deb http://http.debian.net/debian stable main
You may use it like you would use a primary Debian mirror: binaries, sources, stable, testing, experimental, etc., they are all supported.
Backports:http://http.debian.net/debian-backportsArchived releases (archive.debian.org):
http://http.debian.net/debian-archiveSecurity (please read the note below):
http://http.debian.net/debian-security http://security.debian.org/CD images (please read the note below):
http://http.debian.net/debian-cdNotes
Note: some people seem to be testing the above URLs by copying&pasting as-is in their browser. They will fail. You need to add a slash at the end.
There are other approaches to solving the problem of choosing a mirror.
For a comparison to similar tools, like mirrorbrain, please refer to the
README file in the code repository.
cdn.debian.net uses a technology called geoDNS. Although this
technology has its benefits, such as being protocol-independent, it
also has its limitations.
Some of the advantages over such approach include:
Some of the existing advantages over the mirror:// method being developed within apt:
The code does support IPv6 (please refer to the README for the details.) However, the current host doesn't have IPv6 connectivity.
Put simply: World domination.
Well, no, not really. If users like it, they will use it. If they
don't, well, they won't use it. Either way, I had fun learning some of
the necessary bits and coding it.
Oh, and there's still a lot that can be done to improve the redirector.
If you are interested please do clone the repository and get in touch
with me.
There are plans for features such as:
The redirector can not send users to a local address. Use a caching
proxy.
If you don't have control over the network infrastructure, you might
want to look at apt-p2p.
The code repository is now at github. Feel free to clone it, hack it, send pull requests, report bugs (in the code! see below), etc. If you really don't want to create an account there (for whatever reason) you may send me (Raphael) an email, but I might need some prodding.
Clone it:https://github.com/rgeissert/http-redirector.git
If you are having issues with the redirector itself, please email me instead. Hash sum mismatches, poor mirror selection, etc., I'd like to know about all that.
There is no warrant that this service will be uninterrupted or error free. It is provided in the hope that it will be useful but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.