unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Mortimer Cladwell <mbcladwell@gmail.com>, guile-user@gnu.org
Subject: Re: http-request bearer token syntax for Twitter v2 api
Date: Thu, 13 Oct 2022 10:53:40 +0200	[thread overview]
Message-ID: <19ba99f3-215a-cc17-07eb-822a57b34025@telenet.be> (raw)
In-Reply-To: <CAOcxjM5QguZtLEEZyF0j7QH7031gJ6bU2cxhPWSq7g+gz3_fHA@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 811 bytes --]



On 12-10-2022 12:30, Mortimer Cladwell wrote:
> Hi,
> Has anyone successfully submitted a bearer token to Twitter v2 api using
> http-request? What syntax did you use? Without success I have tried many
> permutations/splellings/capitalizations of:

Note that Guile sometimes sends uncapitalised headers (as allowed by the 
relevant RFCs), but some implementations are stricter than permitted by 
the standard and expect capitalisation.  See '[PATCH] web: send 
capitalized authorization scheme':

* https://lists.gnu.org/archive/html/guile-devel/2022-06/msg00020.html
* https://lists.gnu.org/archive/html/guile-devel/2022-06/msg00008.html

Perhaps the same thing is happening here.

It appears that the patch was applied, but I don't know if it's in a 
release yet.

Greetings,
Maxime.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2022-10-13  8:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 10:30 http-request bearer token syntax for Twitter v2 api Mortimer Cladwell
2022-10-12 11:06 ` Olivier Dion via General Guile related discussions
2022-10-12 18:33   ` Mortimer Cladwell
2022-10-13  5:53 ` James Crake-Merani
2022-10-13  8:53 ` Maxime Devos [this message]
2022-10-13 11:37 ` Ricardo Wurmus
2022-10-13 20:42   ` Mortimer Cladwell

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=19ba99f3-215a-cc17-07eb-822a57b34025@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guile-user@gnu.org \
    --cc=mbcladwell@gmail.com \
    /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).