From: Mark H Weaver <mhw@netris.org>
To: Roel Janssen <roel@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Subject: Re: Questions about the (web client) module.
Date: Fri, 21 Jul 2017 00:49:36 -0400 [thread overview]
Message-ID: <87fudqcs2n.fsf@netris.org> (raw)
In-Reply-To: <87h8y691nm.fsf@gnu.org> (Roel Janssen's message of "Fri, 21 Jul 2017 00:36:13 +0200")
Roel Janssen <roel@gnu.org> writes:
>>> 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:
>
> The value I use is "guile-virtuoso-driver". All of the below
> functions work as expected with this value.
>
> Could it be that something else is wrong?
> Here's the entire code I use:
>
> (define* (sparql-query-post query
> #:key
> (host "localhost")
> (port 8890)
> (graph "")
> (type "json"))
> (let ((base-uri (string-append "http://" host ":" (number->string port) ))
> (boundary "guile-virtuoso-driver"))
> (let ((body (string-append
> (format #f
> "--~a~%Content-Disposition: form-data; name=~s~%~%text/csv~%"
> boundary "format")
> (format #f
> "--~a~%Content-Disposition: form-data; name=~s~%~%~a~%--~a~%"
> boundary "query" query boundary))))
> (http-post
> (string-append base-uri "/sparql")
> #:body body
> #:headers `((content-length . ,(string-length body))
> (content-type . "multipart/form-data; boundary=guile-virtuoso-driver")
The line above should be replaced with this:
(content-type . (multipart/form-data (boundary . ,boundary)))
> (Accept . "*/*"))))))
and this should be:
(accept . ((*/*)))
These are the "parsed" form of HTTP headers, where the header names are
lowercase symbols and the associated values are not usually strings but
rather a Scheme representation of the value. See section 7.3.4 (HTTP
Headers) in the Guile manual for more information.
Mark
next prev parent reply other threads:[~2017-07-21 4:49 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
2017-07-20 22:36 ` Roel Janssen
2017-07-21 4:49 ` Mark H Weaver [this message]
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=87fudqcs2n.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--cc=roel@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).