From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] CSTR 122 on CHEM?
Date: Thu, 17 Aug 2017 18:38:30 +0000 [thread overview]
Message-ID: <20170817183829.GD31148@5B3C9D53AD8F45DD93F7082AF345DC1A> (raw)
In-Reply-To: <201708171758.v7HHw8Gi031951@freefriends.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
On 17 Aug 2017 11:58 -0600, from arnold at skeeve.com:
>> http://web.archive.org/web/*/http://cm.bell-labs.com/cm/cs/cstr/122.ps.gz
>
> OK, so how do I actually get the file? I seem to not be able to figure
> out how the Wayback machine works. :-(
Here's a quick way to get the _most recently archived_ version of a
URL from the Wayback Machine:
Take https://web.archive.org/web/99991232235959/
Append the URL of interest, including protocol.
That would be
https://web.archive.org/web/99991232235959/http://cm.bell-labs.com/cm/cs/cstr/122.ps.gz
Feed that to your web browser or other HTTP client.
It will redirect to the most recent version, which in this case
appears to be
https://web.archive.org/web/20070203045131/http://cm.bell-labs.com:80/cm/cs/cstr/122.ps.gz
Alternatively, you need Javascript enabled to see on which dates they
archived the URL in question (that'd be the '*' variant, except I
access the Wayback Machine over HTTPS), then hover over a colored date
to see the list of snapshots on that date, then click the time link to
go to that version of the URL.
They used to have until recently a UI that didn't require executing
client-side Javascript... I suppose that's called progress.
--
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
“People who think they know everything really annoy
those of us who know we don’t.” (Bjarne Stroustrup)
prev parent reply other threads:[~2017-08-17 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:42 arnold
2017-08-17 16:39 ` Steve Simon
2017-08-17 17:52 ` arnold
2017-08-17 17:58 ` arnold
2017-08-17 18:22 ` arnold
2017-08-17 18:48 ` Arthur Krewat
2017-08-17 19:19 ` Kurt H Maier
2017-08-18 10:38 ` arnold
2017-08-17 18:38 ` Michael Kjörling [this message]
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=20170817183829.GD31148@5B3C9D53AD8F45DD93F7082AF345DC1A \
--to=michael@kjorling.se \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).