public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: John Heffner <jheffner@psc•edu>
To: TJ <linux@tjworld•net>
Cc: netdev <netdev@vger•kernel.org>
Subject: Re: Problem with implementation of TCP_DEFER_ACCEPT?
Date: Fri, 24 Aug 2007 12:09:23 -0400	[thread overview]
Message-ID: <46CF02B3.6020101@psc.edu> (raw)
In-Reply-To: <1187947887.6976.18.camel@bagoas.tjworld.net>

TJ wrote:
> Right now Juniper are claiming the issue that brought this to the
> surface (the bug linked to in my original post) is a problem with the
> implementation of TCP_DEFER_ACCEPT.
> 
> My position so far is that the Juniper DX OS is not following the HTTP
> standard because it doesn't send a request with the connection, and as I
> read the end of section 1.4 of RFC2616, an HTTP connection should be
> accompanied by a request.
> 
> Can anyone confirm my interpretation or provide references to firm it
> up, or refute it?

You can think of TCP_DEFER_ACCEPT as an implicit application close() 
after a certain timeout, when not receiving a request.  All HTTP servers 
do this anyway (though I think technically they're supposed to send a 
408 Request Timeout error it seems many do not).  It's a very valid 
question for Juniper as to why their box is failing to fill requests 
when its back-end connection has gone away, instead of re-establishing 
the connection and filling the request.

   -John

  reply	other threads:[~2007-08-24 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  0:08 Problem with implementation of TCP_DEFER_ACCEPT? TJ
2007-08-24  4:40 ` John Heffner
2007-08-24  7:15 ` Lennert Buytenhek
2007-08-24  8:40   ` Alexey Kuznetsov
2007-08-24  9:31     ` TJ
2007-08-24 16:09       ` John Heffner [this message]
2007-09-02  7:30       ` Andi Kleen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46CF02B3.6020101@psc.edu \
    --to=jheffner@psc$(echo .)edu \
    --cc=linux@tjworld$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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