From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Aleix_Conchillo_Flaqu=C3=A9?= Newsgroups: gmane.lisp.guile.devel Subject: Re: [PATCH] web: authorization header scheme should be capitalized Date: Thu, 23 Jun 2022 18:46:23 -0700 Message-ID: References: <20220623202759.3578506-1-aconchillo@gmail.com> <922957d6545149287a6aec7b9d258bf2dd7603ef.camel@telenet.be> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000078a06b05e227bde7" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33723"; mail-complaints-to="usenet@ciao.gmane.io" Cc: guile-devel To: Maxime Devos Original-X-From: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Fri Jun 24 03:48:30 2022 Return-path: Envelope-to: guile-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o4YQv-0008eV-V4 for guile-devel@m.gmane-mx.org; Fri, 24 Jun 2022 03:48:30 +0200 Original-Received: from localhost ([::1]:48438 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o4YQu-0004EK-HQ for guile-devel@m.gmane-mx.org; Thu, 23 Jun 2022 21:48:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42246) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o4YP7-0002gs-Gg for guile-devel@gnu.org; Thu, 23 Jun 2022 21:46:39 -0400 Original-Received: from mail-pl1-x632.google.com ([2607:f8b0:4864:20::632]:46058) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o4YP5-0001PS-PO for guile-devel@gnu.org; Thu, 23 Jun 2022 21:46:37 -0400 Original-Received: by mail-pl1-x632.google.com with SMTP id d5so780133plo.12 for ; Thu, 23 Jun 2022 18:46:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OXqh0av5gr/DtaboxXe2F6HCg+LMZ54n9dySiBh3hPA=; b=W2kD02w/Bn5Xius8naF47Vsn+VJDL0oy3Dc6SzDqbqQ49BwvT4KqflEjK7qe6W34Ze yc7Hk1hYM/jESZwOxWf4vEGnaZRHFzorxMu6V+hynAtUnVbHANyh+avbJlCcXFPz6eYN /fCoRbtgRDjLtjq+vOiWfvj1o70M8nkCKkRkipHJhQfWPs7bWvzWtdd/NV+CrNWxKotT 9lPx13CxF6tsqkEBEqyhFosL1F4c2n4H8P/aL2HYRVADb7FyWRTtYndXHc/2I8cGKB4k CHHWxlw6xDXUY8kcVlTzi9uY/nPw+22RwPMo3naFn4y8O0AO6gropmqixOPUab69sTCe NnGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OXqh0av5gr/DtaboxXe2F6HCg+LMZ54n9dySiBh3hPA=; b=k+xSzWqI5rPiTywqnn4gba9Rc3i11T4c9J+IgEGMBcb0DSZxtb9J6TiEQo8l3wT5kA HVvRjMq3SGWsIEWtpvoDC6gjuj+MKhQD9QS1AEhSFAhxoTqBNjuVOSWssORIDz42ezL2 cIR9HL0szH5lbhbcU0YmtcMI2DWrx8xRng2sv6eYqBXQ7npwlKSAz0lgpSoCzU6Bw0Dv SPRbuDr3od0k1vso8voZT2IJwLBXavf0eIT/EHZJxu2KqRl8kki+kRVu+DofOQPkEk34 7XPSlfofnGp25ztCVqMIlYvVrtIdVMNI4iUVAuvpfEa4+OPuQ4jleoILwcd8DKpKqJqc te9A== X-Gm-Message-State: AJIora/1c+pJlopx4cLD1ir9Mi8k+vj2RL1iIbwRExvgFy7lqXiLszrU 5fKUvv58EEWRdCTluK9aXg10UC7OP8Y76B3+MY0= X-Google-Smtp-Source: AGRyM1sIrbeALiUQmqmn919HAgc9k/+1vAThaueJYUsSULe5uH+p18dcXx9tmKWQEOKY1GoD0QdkIIE9aEeWblbOhoc= X-Received: by 2002:a17:90b:341:b0:1e0:cf43:df4f with SMTP id fh1-20020a17090b034100b001e0cf43df4fmr1027429pjb.126.1656035193953; Thu, 23 Jun 2022 18:46:33 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=2607:f8b0:4864:20::632; envelope-from=aconchillo@gmail.com; helo=mail-pl1-x632.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.io gmane.lisp.guile.devel:21233 Archived-At: --00000000000078a06b05e227bde7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jun 23, 2022 at 3:20 PM Maxime Devos wrote= : > Aleix Conchillo Flaqu=C3=A9 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. > > 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. Best, Aleix --00000000000078a06b05e227bde7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, Jun 23, 2022 at 3:20 PM = Maxime Devos <maximedevos@tele= net.be> wrote:
Aleix Conchillo Flaqu=C3=A9 schreef op do 23-06-2022 om 14:13 [-0700]= :
> https://community.spotify.com/t5/Spotify-for-De= velopers/API-Authorization-header-doesn-t-follow-HTTP-spec/m-p/5397381#M491= 7
> > Also, there's still a potential patch to be had, e.g. you cou= ld add
> > a test checking that Guile properly supports schemes in other cas= es
> > (if not done already).
>
> What do you mean?

Even if there is nothing that _has_ to be done in Guile, there's still<= br> 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.


Ah, got it. Yes, that would make sense.<= /div>

I was thinking about it again. I know that Guile compl= ies with the standard but since, I would say, capitalized schemes is what m= ost libraries use, would it make sense to switch to that? I don't reall= y expect big companies to fix this kind of stuff fast and in the meantime w= e can't use Guile for certain things. I have to say I've never seen= lowercase Authorization header schemes.

Best,

Aleix
--00000000000078a06b05e227bde7--