From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] TUHS web server has changed
Date: Mon, 9 May 2022 13:57:59 -0600 [thread overview]
Message-ID: <d2d76d75-f6e4-3ac3-df51-dac94929227c@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CAMQbRb0C5N+BPrLjf3EzDcR2zNheg4CH4KnapjzBX7Syvp9++w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On 5/9/22 11:55 AM, Kenneth Goodwin wrote:
> Url rewriting
Yes.
> That would mean supporting that forever including the overhead in
> contrast to the "SED modify the archive" approach is a one shot or so deal.
I'm concerned with supporting the URLs that are in all of the emails
that have been sent out over the years that point back to the archive.
sed won't change what's in someone else's email box. URL rewriting will
make sure that was was sent out in the past will continue to work in the
future. ;-)
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4017 bytes --]
next prev parent reply other threads:[~2022-05-09 20:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 2:08 Warren Toomey via TUHS
2022-05-04 13:27 ` Clem Cole
2022-05-04 19:37 ` Mary Ann Horton
2022-05-05 0:52 ` Dave Horsfall
2022-05-05 5:43 ` Andy Kosela
2022-05-05 5:57 ` Grant Taylor via TUHS
2022-05-05 20:48 ` Dave Horsfall
2022-05-04 17:54 ` Grant Taylor via TUHS
2022-05-05 21:26 ` Warren Toomey via TUHS
2022-05-05 23:42 ` Gregg Levine
2022-05-06 2:38 ` Grant Taylor via TUHS
2022-05-06 2:52 ` Warner Losh
2022-05-06 4:32 ` Kenneth Goodwin
2022-05-07 16:13 ` Patrick Audley via TUHS
2022-05-09 16:12 ` Grant Taylor via TUHS
2022-05-09 17:55 ` Kenneth Goodwin
2022-05-09 19:22 ` Richard Salz
2022-05-09 19:57 ` Grant Taylor via TUHS [this message]
2022-05-09 18:37 ` Danil Smirnov
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=d2d76d75-f6e4-3ac3-df51-dac94929227c@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).