public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pauln@truemesh.com>
To: linux-8086@vger.kernel.org
Subject: Re: webserver stalls
Date: Mon, 14 Oct 2002 23:20:29 +0100	[thread overview]
Message-ID: <20021014222029.GE12349@raq465.uk2net.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210140140090.22022-100000@olympus.btstream.com>

On Mon, Oct 14, 2002 at 01:41:49AM -0700, jb1@btstream.com wrote:
> The ELKS webserver stalls when I access the 266-byte sample web page from
> Red Hat 7.0 (see below for versions). The problem seems to be related to
> the "Content-Length", which is apparently equal to the size of the web
> page file. If the file size is less than 100 then both "get /"  from
> telnet and lynx (a browser) display the file as expected; if the file size
> is 100 or larger then both stall. Both lynx and telnet work properly with 
> everything I've tried except ELKS.

Thanks for such a detailed report, I'll see if I can replicate this on
my setup - but that probably won't be untill the weekend.

Paul

      reply	other threads:[~2002-10-14 22:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-14  8:41 webserver stalls jb1
2002-10-14 22:20 ` Paul Nasrat [this message]

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=20021014222029.GE12349@raq465.uk2net.com \
    --to=pauln@truemesh.com \
    --cc=linux-8086@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