Home |
Licence |
FAQ |
Docs |
Download |
Keys |
Links
Mirrors |
Updates |
Feedback |
Changes |
Wishlist |
Team
Here is a list of PuTTY web site mirrors. I add to this list when people tell me mirrors exist: I don't go out looking for them. If you want to mirror the PuTTY site, you're welcome to - tell me about it and I'll put it on the list. Be sure to read the mirroring guidelines below.
The official PuTTY home site, in case that isn't where you're reading this, is
HTTP mirrors of the whole site:
Be aware that the mirrors are not updated instantly. Also, in many cases, none of the FTP links on the Download page have been mirrored - they still point to the same places as on the original web site. (The HTTP links on the Download page have been mirrored.)
FTP mirrors of the PuTTY releases:
HTTP mirrors of the PuTTY development snapshots:
FTP mirrors of the PuTTY development snapshots:
The preferred (and simplest) way to mirror the PuTTY website is to use
rsync.
We provide a version of the website content
intended for use as a standalone mirror, at
rsync://rsync.chiark.greenend.org.uk/ftp/users/sgtatham/putty-website-mirror.
So you could set up a mirror by running a cron job which
issued a command something like this every day:
rsync -auH rsync://rsync.chiark.greenend.org.uk/ftp/users/sgtatham/putty-website-mirror/ .
You should run this command inside the directory where you
plan to put the mirror; when that command is run, it will fill the
current directory with HTML files and subdirectories. Alternatively,
you can replace . with the name of the target directory.
If you use the above command to fetch our pre-packaged mirror site,
it will only work as designed if your web server is Apache: the site
contains a .htaccess file which handles a couple of
non-obvious MIME types and deals with making the virtual
subdirectory "latest" redirect to the current latest
release. If you do not use Apache, you will have to reproduce this
behaviour in some other way suitable for your own web server.
(We prefer that the "latest" redirect be handled as an
HTTP-visible redirect, rather than a server-side filesystem tweak such
as a symlink, for better behaviour in the face of web caches.)
Alternatively, you can mirror our web site using
GNU wget.
This is less bandwidth-efficient, as unlike rsync
it's not incremental. It's also more difficult, because our binary
downloads are hosted on a different server for bandwidth reasons, so a
conventional "wget -r" will not fetch them at all. Instead,
you will need at least two invocations of wget. Also, as
mentioned above, the release binaries appear to be stored in a
virtual directory called "latest", but this actually
returns an HTTP temporary redirect to a numbered directory such as
"0.53". Ideally a mirror should reproduce this
behaviour as well.
Here is a sample Bourne shell script to create a working PuTTY
mirror site with the binaries in the right place and the HTTP
redirect set up correctly. This script requires sed,
perl and GNU wget, and it also assumes
your web server is Apache (as above). Unlike the above
rsync command, this script will create a subdirectory
called "putty" in the current directory, and place all
the PuTTY web site files inside that subdirectory.
We normally suggest that wget mirrors are updated around
once a week, and no less often than once a month. You can also subscribe
to our mailing list to receive notification
of new releases.
Before notifying us of your mirror, please test that it works: