From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] webfs: add 'headers' file
Date: Sun, 10 Jan 2021 13:11:07 -0800 [thread overview]
Message-ID: <5D539F3B5C5BE2EC03CA37F0E865840A@eigenstate.org> (raw)
In-Reply-To: <f651aea62e5961d8@orthanc.ca>
Quoth Lyndon Nerenberg <lyndon@orthanc.ca>:
> > One other thought that I just had: What if we picked
> > a few of the mandatory or very common headers (contenttype,
> > etc) and put them explicitly in the request dir, and
> > moved the rest to a less-mangled headers subdir?
>
> If we're going to have a headers/... directory do we really need
> to duplicate some of those files elsewhere? For consistency's
> sake I'd just keep 'em all in the one directory and call it a day.
>
> --lyndon
>
We don't need to -- but how many scripts and programs are we
willing to break, and how badly?
next prev parent reply other threads:[~2021-01-10 21:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 18:32 telephil9
2021-01-10 19:28 ` ori
2021-01-10 19:51 ` ori
2021-01-10 20:30 ` Lyndon Nerenberg
2021-01-10 21:11 ` ori [this message]
2021-01-10 22:29 ` Lyndon Nerenberg
2021-01-11 0:50 ` hiro
2021-01-10 21:16 ` Steve Simon
2021-01-11 17:13 ` ori
2021-01-11 21:53 ` cinap_lenrek
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=5D539F3B5C5BE2EC03CA37F0E865840A@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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).