unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
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: Thu, 23 Jun 2022 22:45:10 +0200	[thread overview]
Message-ID: <a722ad4b7108af91ecbfacc2bacf2cba3c37e785.camel@telenet.be> (raw)
In-Reply-To: <CA+XASoWev138jKkf1k4=44u5ZjGKh_dRQ-V79Xubv5vr4gEJ8Q@mail.gmail.com>

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

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?

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).

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-06-23 20:45 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 [this message]
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é
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=a722ad4b7108af91ecbfacc2bacf2cba3c37e785.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).