netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.17.1: fails to fully get webpage
Date: Thu, 29 Jun 2006 10:50:00 -0400	[thread overview]
Message-ID: <44A3E898.1020202@tmr.com> (raw)
In-Reply-To: <20060629041827.GJ2149@zip.com.au>

CaT wrote:
> On Wed, Jun 28, 2006 at 08:47:09PM -0700, David Miller wrote:
>> You can save yourself that hassle by informing the site admin
>> of the affected site that they have a firewall that misinterprets
>> the RFC standard window scaling field of the TCP headers.  These
>> devices assume it is zero because they don't remember the window
>> scale negotiated at the beginning of the TCP connection.
>>
>> Your TCP performance will suffer greatly if you disable window
>> scaling across the board.  It means that only a 64K window will
>> be usable by TCP, and you'll not be able to fill the pipe.
>>
>> Please don't use a screwdriver to pound in a nail :)
> 
> Indeed. The hassle I'm thinking of is the reverse situation (and please
> correct me if this does not apply). Say for example I run a web server.
> I have customers and they have customers (lets call them CCs :). Somewhere
> along the path between me and CCs there is such a misbehaving device.
> The CCs try to get to my customers website and fail (I assume). If my
> assumption is right, what's the probability of the CCs ever informing my
> customer that there is a problem? I think it's more likely they would
> just move on to another site offering the same thing, especially since
> they would mostlikely need to load the site in order to get the
> appropriate contact details.
> 
> Basically the mostlikely end-result is I don't know what there is a
> problem and my customer doesn't know that there is a problem but they're
> just not getting as many hits to their site that they otherwise would.
> 
> Ofcourse, this all depends if such a situation is possible. If it is
> possible would it affect dns and mail in a similar manner too?
> 
I'm glad David Miller clarified this, because I was about to send a 
"don't do that" followup ;-)

But your example is misleading, or at least doesn't reflect customers I 
know. While a few clients with broken network connections may be 
unhappy, disabling scaling will make your web server really, really, 
slow, and that will make everyone unhappy. Particularly if the web 
content is flash or 2MB jpegs, or other ill-chosen stuff. You don't want 
people to think you are running at dial-up speeds.

-- 
Bill Davidsen <davidsen@tmr.com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.



  reply	other threads:[~2006-06-29 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29  1:59 2.6.17.1: fails to fully get webpage CaT
2006-06-29  2:46 ` David Miller
2006-06-29  3:09   ` CaT
2006-06-29  3:47     ` David Miller
2006-06-29  4:18       ` CaT
2006-06-29 14:50         ` Bill Davidsen [this message]
2006-06-29 22:50           ` CaT
2006-07-05  0:55             ` possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage) CaT
2006-07-05 11:54               ` linux-os (Dick Johnson)
2006-07-10 23:23                 ` CaT
2006-07-13 12:11               ` possible dos / wsize affected frozen connection length Herbert Xu

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=44A3E898.1020202@tmr.com \
    --to=davidsen@tmr.com \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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 NNTP newsgroup(s).