From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] webfs: add 'headers' file
Date: Sun, 10 Jan 2021 11:51:33 -0800 [thread overview]
Message-ID: <C69E941D1C13F18DB89329C3B2760487@eigenstate.org> (raw)
In-Reply-To: <BDC9EB3C9F2C3DB8CE03CE4C7225B80B@eigenstate.org>
Quoth ori@eigenstate.org:
> The problem there is compatibility: it's going to be a
> pain to transition to a more usable scheme. So maybe we
> live with the wart, or present both ways?
>
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?
next prev parent reply other threads:[~2021-01-10 20:22 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 [this message]
2021-01-10 20:30 ` Lyndon Nerenberg
2021-01-10 21:11 ` ori
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=C69E941D1C13F18DB89329C3B2760487@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).