From: Maxime Devos <maximedevos@telenet.be>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] web: authorization header scheme should be capitalized
Date: Fri, 24 Jun 2022 00:20:20 +0200 [thread overview]
Message-ID: <c116285eb15da8b95ce234024a5a2bcb4526161c.camel@telenet.be> (raw)
In-Reply-To: <CA+XASoVyR_-MfZAZX2L5ACNU-Di6+ipvDY2ceh-d=3ner4ge=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
Aleix Conchillo Flaqué schreef op do 23-06-2022 om 14:13 [-0700]:
> 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?
Even if there is nothing that _has_ to be done in Guile, there's still
thing that _can_ be done in Guile to improve Guile's test suite -- in
this case, a test in the test suite that the Guile's web code
understands both lowercase and uppercase and titlecase authorisation
schemes.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-23 22:20 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 [this message]
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=c116285eb15da8b95ce234024a5a2bcb4526161c.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=aconchillo@gmail.com \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).