On Monday 05 October 2009, Jim Jagielski wrote:
Thx... I'm updating it with an eye to making it core, and
therefore having ReqTimeout headerinit=5 headermax=10
As we also have RequestHeaders, maybe RequestTimeout would be better?
Let me know if I can help w/ the docs.
I have commited
Thx... I'm updating it with an eye to making it core, and
therefore having ReqTimeout headerinit=5 headermax=10
Let me know if I can help w/ the docs.
On Oct 4, 2009, at 3:40 PM, Stefan Fritsch wrote:
On Sunday 04 October 2009, Nick Kew wrote:
FWIW, IMO it should go in modules/filters
On 10/04/2009 10:23 AM, Stefan Fritsch wrote:
Hi,
I would like to add mod_reqtimeout [1,2] to trunk. Is this OK?
Considering the positive comments it received, may I put it into
modules/filter or should it go into modules/experimental first?
I guess experimental is a good starting
+1
Rainer Jung wrote:
On 04.10.2009 10:23, Stefan Fritsch wrote:
Hi,
I would like to add mod_reqtimeout [1,2] to trunk. Is this OK?
I think it would be a useful addition.
Regards,
Rainer
On 4 Oct 2009, at 09:23, Stefan Fritsch wrote:
Hi,
I would like to add mod_reqtimeout [1,2] to trunk. Is this OK?
Considering the positive comments it received, may I put it into
modules/filter or should it go into modules/experimental first?
experimental has been somewhat in limbo of
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
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
On Oct 4, 2009, at 2:38 PM, Stefan Fritsch wrote:
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
Jim Jagielski wrote:
And I would prefer several config directives instead of having to
remember which value in Timeout means what.
Well, I'm not a big fan of directive creep, but I see your point
and agree with it in a general sense.
Timeout Thistimeout=10 Thattimeout=2 Othertimeout=300 ?
Jim Jagielski wrote:
On Oct 4, 2009, at 2:38 PM, Stefan Fritsch wrote:
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
On Sunday 04 October 2009, Nick Kew wrote:
FWIW, IMO it should go in modules/filters not experimental.
+1. trunk is, by definition, experimental. But when we
float off 2.3/4-branch, we should perhaps do some documentation
of stability levels of different features and modules for users.
I
11 matches
Mail list logo