From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 32528@debbugs.gnu.org
Subject: bug#32528: http-post breaks with XML response payload containing boundary
Date: Tue, 25 Jun 2019 10:25:06 +0200 [thread overview]
Message-ID: <87imsuqdgd.fsf@gnu.org> (raw)
In-Reply-To: <875zztg8bw.fsf@netris.org> (Mark H. Weaver's message of "Tue, 28 Aug 2018 23:28:19 -0400")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
>>From 6af35a3997887fe24620fc7448ded3649e04b82b Mon Sep 17 00:00:00 2001
> From: Mark H Weaver <mhw@netris.org>
> Date: Tue, 28 Aug 2018 23:15:36 -0400
> Subject: [PATCH 2/2] PRELIMINARY: web: Fix parsing of HTTP Content-Type
> header.
>
> ---
> module/web/http.scm | 109 +++++++++++++++++++++++++++++++++++---------
> 1 file changed, 88 insertions(+), 21 deletions(-)
This patch would be nice to have, if and when you can complete it.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-06-25 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 8:49 bug#32528: http-post breaks with XML response payload containing boundary Ricardo Wurmus
2018-08-28 21:51 ` Mark H Weaver
2018-08-29 3:28 ` Mark H Weaver
2019-06-25 8:25 ` Ludovic Courtès [this message]
2018-08-29 10:26 ` Ricardo Wurmus
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=87imsuqdgd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32528@debbugs.gnu.org \
--cc=mhw@netris.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).