From: John Fieber <jfieber@adobe.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: TCP reset and socket buffer draining responsibility
Date: Mon, 15 Mar 2010 07:32:06 -0700 [thread overview]
Message-ID: <D476A0C6-7D74-464D-B962-96D5EF9E5F92@adobe.com> (raw)
I have a bug where some Rack middleware that determines certain PUT/POST error responses without needing to read the request body. On Linux, this causes a TCP reset when Unicorn closes the socket with unread data in the input buffer. The reset preempts the delivery written but still buffered response, so client receives a simple RST and no response. If I inject some read-buffer draining code just before the close, the problem goes away.
The RST behavior is obviously not desired, but my question is what level of the stack is responsible for making sure it doesn't happen? It strikes me that Unicorn is in the best position to do it efficiently and reliably, but anything higher up can also do it.
Thoughts?
-john
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next reply other threads:[~2010-03-15 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 14:32 John Fieber [this message]
2010-03-15 17:48 ` TCP reset and socket buffer draining responsibility Eric Wong
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://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D476A0C6-7D74-464D-B962-96D5EF9E5F92@adobe.com \
--to=jfieber@adobe.com \
--cc=mongrel-unicorn@rubyforge.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
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).