From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: guile-www 1.1.1ttn3 available
Date: Tue, 03 Dec 2002 20:10:54 -0800 [thread overview]
Message-ID: <E18JQsA-0003R2-00@giblet> (raw)
the http 1.1 spec (rfc 2616) is 176 pages; it will be a while before
guile-www http implementation gets there... however, for now, we have a
new proc to play with: http:post-form. example usage:
(http:post-form (url:parse "http://www.biomail.org")
(list "User-Agent: biomail2ris/1.0")
'((uid . 2342433)
(uid . 8193)
(submit . "Medline format")
(user . "jrandom")
(mail . "jrandom@some.org")
(subj . "integrin AND rap1")
(lang . "")))
first arg is a url object. second arg is a list of additional headers
("Content-Type" and "Host" are set automatically). third arg is a list
of key-value pairs, to be rendered as "~A=~A", concatenated with "&",
and urlencoded in the body of an http request. thanks go to w3m folks
for a convenient #ifdef HTTP_DEBUG in url.c. tarball in:
http://www.glug.org/alt/
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
reply other threads:[~2002-12-04 4:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E18JQsA-0003R2-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).