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: Thu, 23 Jun 2022 14:13:41 -0700 [thread overview]
Message-ID: <CA+XASoVyR_-MfZAZX2L5ACNU-Di6+ipvDY2ceh-d=3ner4ge=Q@mail.gmail.com> (raw)
In-Reply-To: <a722ad4b7108af91ecbfacc2bacf2cba3c37e785.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Thu, Jun 23, 2022 at 1:45 PM Maxime Devos <maximedevos@telenet.be> wrote:
> Aleix Conchillo Flaqué schreef op do 23-06-2022 om 13:42 [-0700]:
> >
> > [...]
> > I think you are right. The spec says clearly that it should be case
> > insensitive.
> >
> > So, disregard this patch.
>
> TBC, did you encounter problems in the wild that made you write the
> patch?
>
>
Yes, and I just posted it here:
https://community.spotify.com/t5/Spotify-for-Developers/API-Authorization-header-doesn-t-follow-HTTP-spec/m-p/5397381#M4917
> Also, there's still a potential patch to be had, e.g. you could add a
> test checking that Guile properly supports schemes in other cases (if
> not done already).
>
>
What do you mean?
Aleix
[-- Attachment #2: Type: text/html, Size: 2039 bytes --]
next prev parent reply other threads:[~2022-06-23 21:13 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é [this message]
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é
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+XASoVyR_-MfZAZX2L5ACNU-Di6+ipvDY2ceh-d=3ner4ge=Q@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).