Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Stefan Fritsch <sf@sfritsch.de>
To: dev@httpd.apache.org
Subject: Re: adding mod_reqtimeout to trunk?
Date: Sun, 4 Oct 2009 20:38:59 +0200
User-Agent: KMail/1.12.1 (Linux/2.6.30-1-686; KDE/4.3.1; i686; ; )
References: <200910041023.28607.sf@sfritsch.de>
 <95CE6505-D091-480E-AFF6-B2D59B1FD1CE@jaguNET.com>
In-Reply-To: <95CE6505-D091-480E-AFF6-B2D59B1FD1CE@jaguNET.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200910042039.00259.sf@sfritsch.de>

On Sunday 04 October 2009, Jim Jagielski wrote:
> Personally, I'd like to see this as part of the actual
> code core, where we have several Timeouts, eg:
> 
>         Timeout 30 5 10 2
> 
> which define timeout as now, timeout before 1st byte, timeout
> between bytes timeout after etc...
> 
> We've always wanted better control over this ind timeouts and
> putting it in a module seems not a good idea for 2.4/3.0
> (but of course, OK for 2.2.x)
> 

I think putting mod_reqtimeout into trunk until it is backported to 
2.2 and then moving it into the core would make sense, wouldn't it?

And I would prefer several config directives instead of having to 
remember which value in Timeout means what.