From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Questions about the (web client) module.
Date: Thu, 20 Jul 2017 17:41:09 +0200 [thread overview]
Message-ID: <878tjjru96.fsf@gnu.org> (raw)
In-Reply-To: 87o9sfxtuk.fsf@gnu.org
Hi Roel,
Roel Janssen <roel@gnu.org> skribis:
> When I use http-post, and I want to change the HTTP header called
> "Content-Type", I seem to need to spell it as "content-type" in the
> #:headers part of the 'http-post' section. Other headers like "Accept"
> do not seem to follow the same lowercase style route.
>
> More confusingly, using something like:
> #:headers '((Content-Type . "text/csv"))
>
> leads to outputting the "Content-Type" header twice.
> Why is "content-type" special?
‘sanitize-request’ in (web client) adds a ‘Content-Type’ header if there
is none.
As for lower-case, perhaps the ‘request’ procedure in (web client)
should automatically convert to lower-case, or perhaps we should simply
clarify the documentation here.
> Then my next question is about "multipart/form-data" content types.
> My code looks like this:
>
> #:headers `((content-type . ,(string-append
> "multipart/form-data; boundary=" boundary))
> (Accept . "*/*"))
>
> But that does not work:
> scheme@(guile-user)>
> web/request.scm:184:10: In procedure build-request:
> web/request.scm:184:10: Bad request: Bad value for header content-type: "multipart/form-data; boundary=..."
>
> This is, however, a valid Content-Type.
What’s the value of ‘boundary’? At first sight it looks good to me:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,use(web http)
scheme@(guile-user)> (valid-header? 'content-type (parse-header 'content-type "text/plain"))
$13 = #t
scheme@(guile-user)> (valid-header? 'content-type (parse-header 'content-type "multipart/form-data; boundary=2"))
$14 = #t
scheme@(guile-user)> (valid-header? 'content-type (parse-header 'content-type "multipart/form-data; boundary=sdfd"))
$15 = #t
scheme@(guile-user)> (parse-header 'content-type "multipart/form-data; boundary=sdfd")
$16 = (multipart/form-data (boundary . "sdfd"))
--8<---------------cut here---------------end--------------->8---
HTH!
Ludo’.
next prev parent reply other threads:[~2017-07-20 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 10:53 Questions about the (web client) module Roel Janssen
2017-07-20 15:41 ` Ludovic Courtès [this message]
2017-07-20 22:36 ` Roel Janssen
2017-07-21 4:49 ` Mark H Weaver
2017-07-21 5:05 ` Mark H Weaver
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=878tjjru96.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).