unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Hartwig <mandyke@gmail.com>
To: Andy Wingo <wingo@pobox.com>, Jason Earl <jearl@notengoamigos.org>
Cc: 13857@debbugs.gnu.org
Subject: bug#13857: Unhandled case in module/web/response.scm
Date: Sun, 10 Mar 2013 08:04:41 +0800	[thread overview]
Message-ID: <CAN3veRcJsJxs_Nq2VdrXhq6Oo_wVnDU+Yq=Zaph7fgF9OfQv7Q@mail.gmail.com> (raw)
In-Reply-To: <87r4jo6uy0.fsf@notengoamigos.org>

On 10 March 2013 06:59, Jason Earl <jearl@notengoamigos.org> wrote:
> On Sat, Mar 09 2013, Andy Wingo wrote:
>
>> On Sat 09 Mar 2013 02:27, Daniel Hartwig <mandyke@gmail.com> writes:
>>
>>> It is anyway clear that ‘response-body-port’ is missing the case where
>>> a content-length header is not present and the body is terminated by
>>> the server closing the port.  Some additional care needs to be taken,
>>> e.g. ‘#:keep-alive?’ is incompatible with missing content-length.
>>> Depending on how ‘response-body-port’ is used, I will have to consider
>>> whether to signal an error or do something else in that case.
>>>
>>> Thanks for reporting this and hopefully it can be fixed for the next
>>> point release.  As I am currently somewhat involved with the web
>>> modules and related RFCs it is something else I can work on.
>>
>> Something like this?
>>
>> [patch]

Yes, more or less.  :-)





  reply	other threads:[~2013-03-10  0:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02  7:21 bug#13857: Unhandled case in module/web/response.scm Jason Earl
2013-03-03  0:47 ` Daniel Hartwig
2013-03-03  4:55   ` Jason Earl
2013-03-09  1:27     ` Daniel Hartwig
2013-03-09 10:15       ` Andy Wingo
2013-03-09 22:59         ` Jason Earl
2013-03-10  0:04           ` Daniel Hartwig [this message]
2013-03-10 18:24           ` Andy Wingo
2013-03-05 19:04   ` Jason Earl

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='CAN3veRcJsJxs_Nq2VdrXhq6Oo_wVnDU+Yq=Zaph7fgF9OfQv7Q@mail.gmail.com' \
    --to=mandyke@gmail.com \
    --cc=13857@debbugs.gnu.org \
    --cc=jearl@notengoamigos.org \
    --cc=wingo@pobox.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).