unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] web: authorization header scheme should be capitalized
Date: Fri, 24 Jun 2022 06:41:02 -0700	[thread overview]
Message-ID: <CA+XASoU7Ouh9DLD=u=TPGRfJt_0XONNC04EoSM0yWY0e_p93tA@mail.gmail.com> (raw)
In-Reply-To: <32d2790b6941f5bf5b9185bd1fc9f46d90fcc85e.camel@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 971 bytes --]

On Fri, Jun 24, 2022 at 1:35 AM Maxime Devos <maximedevos@telenet.be> wrote:

> Aleix Conchillo Flaqué schreef op do 23-06-2022 om 18:46 [-0700]:
> > Ah, got it. Yes, that would make sense.
> >
> > I was thinking about it again. I know that Guile complies with the
> > standard but since, I would say, capitalized schemes is what most
> > libraries use, would it make sense to switch to that? I don't really
> > expect big companies to fix this kind of stuff fast and in the
> > meantime we can't use Guile for certain things. I have to say I've
> > never seen lowercase Authorization header schemes.
>
> As long as we remember to _also_ report the bug in the buggy
> ‘consumers’ of the header (in this case, those big companies) and
> remember that lower-case isn't buggy, switching to the more
> conventional title-case seems sensible to me.
>
>
Great. I'll re-word the patch then and add your suggested additional tests.

Thank you!

Aleix

[-- Attachment #2: Type: text/html, Size: 1843 bytes --]

  reply	other threads:[~2022-06-24 13:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 20:27 [PATCH] web: authorization header scheme should be capitalized Aleix Conchillo Flaqué
2022-06-23 20:33 ` Aleix Conchillo Flaqué
2022-06-23 20:40 ` Maxime Devos
2022-06-23 20:42   ` Aleix Conchillo Flaqué
2022-06-23 20:45     ` Maxime Devos
2022-06-23 21:13       ` Aleix Conchillo Flaqué
2022-06-23 22:20         ` Maxime Devos
2022-06-24  1:46           ` Aleix Conchillo Flaqué
2022-06-24  8:35             ` Maxime Devos
2022-06-24 13:41               ` Aleix Conchillo Flaqué [this message]
2022-06-24 12:16             ` Dr. Arne Babenhauserheide
  -- strict thread matches above, loose matches on Subject: below --
2022-06-23 19:15 Aleix Conchillo Flaqué

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+XASoU7Ouh9DLD=u=TPGRfJt_0XONNC04EoSM0yWY0e_p93tA@mail.gmail.com' \
    --to=aconchillo@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).