unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Darren Hoo <darren.hoo@gmail.com>
To: guile-user@gnu.org
Subject: Re: An http session that ends with a TCP Reset sent by the server
Date: Sun, 16 Jun 2013 11:17:32 +0800	[thread overview]
Message-ID: <m21u82iw1f.fsf@gmail.com> (raw)
In-Reply-To: 87zjusd5nr.fsf@tines.lan

Mark H Weaver <mhw@netris.org> writes:

Hi Mark,

Thanks,

>
> While it is true that the RFCs allow a TCP connection to be "aborted" by
> a RST segment, this is an error condition.  It's not a proper way to end
> an HTTP connection under normal circumstances.
>
> I believe the server you are trying to talk to is violating the HTTP
> protocol.  Among other things, I believe that a RST segment may cause
> the receiving side to discard any input buffers that have not yet been
> read by the client.

Yes it is violateing the protocol. Sorry to have not mentioned that the
response recieved is from the firewall not the real server.

> I see nothing in RFC 2616 that allows this behavior.  In fact, section
> 10.4 explicitly mentions the danger that resetting the connection may
> cause data loss.
>
>> My question is how I can I handle this, ie, read the response body
>> and ignore  the RST
>> in Guile without changing anything in libguile?
>
> I'm sorry, but I don't see an easy way to work around this problem
> (which doesn't necessarily mean it can't be done).
>
> Out of curiosity, do you know what software is running on this server?
>
> Have you checked to see whether the server resets the connection when
> talking to a different HTTP client?
>

Yes, both curl and brower receive RST but do not report anything
conceivable to the user.

I think there's no elegant way to deal with this condition with Guile,
maybe I should try other alternative to work around this.





  reply	other threads:[~2013-06-16  3:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  8:33 An http session that ends with a TCP Reset sent by the server Darren Hoo
2013-06-14 16:21 ` Mark H Weaver
2013-06-16  3:17   ` Darren Hoo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-06-13 10:23 Darren Hoo

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=m21u82iw1f.fsf@gmail.com \
    --to=darren.hoo@gmail.com \
    --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).