From: Kenneth Goodwin <kennethgoodwin56@gmail.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] TUHS web server has changed
Date: Mon, 9 May 2022 13:55:42 -0400 [thread overview]
Message-ID: <CAMQbRb0C5N+BPrLjf3EzDcR2zNheg4CH4KnapjzBX7Syvp9++w@mail.gmail.com> (raw)
In-Reply-To: <67d0b1b5-e1b1-ebb4-6ebd-aba2fbd111ee@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
Url rewriting
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.
On Mon, May 9, 2022, 12:15 PM Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
wrote:
> On 5/7/22 10:13 AM, Patrick Audley via TUHS wrote:
> > When I saw this, I started to think, "I bet we can make a regexp for
> that".
>
> :-D
>
> > Apparently, I do too much text processing.
>
> Na. I don't think so. Text processing seems to be one (of the many)
> thing(s) that Unix, et al., excel at. So I think it's probably natural
> for anyone well versed in Unix ... to think "RegEx"!
>
> > I'm up for helping process the archive if needed with sed, perl or
> > some such.
>
> I think we're thinking about two different layers of actions. Both
> using their own form of RegEx like behavior.
>
> It sounds like you're talking about processing / munging an mbox mail
> archive.
>
> I'm thinking about URL re-writing in the web server, be it on the fly or
> static configuration (for fixed list of old URLs).
>
>
>
> --
> Grant. . . .
> unix || die
>
>
[-- Attachment #2: Type: text/html, Size: 1637 bytes --]
next prev parent reply other threads:[~2022-05-09 17:58 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 [this message]
2022-05-09 19:22 ` Richard Salz
2022-05-09 19:57 ` Grant Taylor via TUHS
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=CAMQbRb0C5N+BPrLjf3EzDcR2zNheg4CH4KnapjzBX7Syvp9++w@mail.gmail.com \
--to=kennethgoodwin56@gmail.com \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@minnie.tuhs.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 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).