Le 18/03/2013 22:43, Stefan Fritsch a écrit :
On Thursday 14 March 2013, you wrote:
BTW, I tried to activate pool debug with using
|-enable-pool-debug=all but the server crashes while starting on
my test machine.
Do you know if it is supposed to work (and I do something wrong) or
no one uses
On Mar 18, 2013, at 4:56 PM, Stefan Fritsch s...@sfritsch.de wrote:
Alternatively,
mod_reqtimeout could offer an API to allow modules to disable it. But
I think that is the worse of the two solutions.
Actually, I think that's the most logical solution...
This would be EXTREMELY easy just using -notes
On Mar 19, 2013, at 9:03 AM, Jim Jagielski j...@jagunet.com wrote:
On Mar 18, 2013, at 4:56 PM, Stefan Fritsch s...@sfritsch.de wrote:
Alternatively,
mod_reqtimeout could offer an API to allow modules to disable it. But
I think that is the
On Tue, Mar 19, 2013 at 9:56 AM, j...@apache.org wrote:
Author: jim
Date: Tue Mar 19 13:56:29 2013
New Revision: 1458284
URL: http://svn.apache.org/r1458284
Log:
Allow modules to pro-actively bypass the reqtimeout filter (by connection)
Modified:
Oops... yeah, did this too fast ;)
As far as which makes the most sense, (call-by-call
or forever), both would be best...
On Mar 19, 2013, at 12:16 PM, Jeff Trawick traw...@gmail.com wrote:
On Tue, Mar 19, 2013 at 9:56 AM, j...@apache.org wrote:
Author: jim
Date: Tue Mar 19 13:56:29 2013
Jeff Trawick wrote:
On Tue, Mar 19, 2013 at 9:56 AM, j...@apache.org wrote:
Author: jim
Date: Tue Mar 19 13:56:29 2013
New Revision: 1458284
URL: http://svn.apache.org/r1458284
Log:
Allow modules to pro-actively bypass the reqtimeout filter (by connection)
Modified:
I've added bypassing and removing... for flexibility.
On Mar 19, 2013, at 12:52 PM, Ruediger Pluem rpl...@apache.org wrote:
Jeff Trawick wrote:
On Tue, Mar 19, 2013 at 9:56 AM, j...@apache.org wrote:
Author: jim
Date: Tue Mar 19 13:56:29 2013
New Revision: 1458284
URL:
On 19 Mar 2013, at 7:09 PM, Jim Jagielski j...@jagunet.com wrote:
I've added bypassing and removing... for flexibility.
Is there a generic way for modules to figure out for themselves whether they
should be caring about a particular request or connection?
In other words, if reqtimeout had a
On Mar 19, 2013, at 1:15 PM, Graham Leggett minf...@sharp.fm wrote:
On 19 Mar 2013, at 7:09 PM, Jim Jagielski j...@jagunet.com wrote:
I've added bypassing and removing... for flexibility.
Is there a generic way for modules to figure out for themselves whether they
should be caring about
On 19 Mar 2013, at 7:44 PM, Jim Jagielski j...@jagunet.com wrote:
Agreed... The conn_rec includes a bunch of HTTP related fields
which could serve as such, but the main issue, I think, is
that websockets starts off as HTTP and then changes, so the
initial conn_rec info is HTTP, it's just that
On Mar 19, 2013, at 1:50 PM, Graham Leggett minf...@sharp.fm wrote:
On 19 Mar 2013, at 7:44 PM, Jim Jagielski j...@jagunet.com wrote:
Agreed... The conn_rec includes a bunch of HTTP related fields
which could serve as such, but the main issue, I think, is
that websockets starts off as HTTP
For those of us not familiar how would this be accomplished? Is it just
config or is there also some dev that needs to happen?
On Mar 19, 2013 9:09 AM, Jim Jagielski j...@jagunet.com wrote:
This would be EXTREMELY easy just using -notes
On Mar 19, 2013, at 9:03 AM, Jim Jagielski
Hi --
I notice we have the .wmz and .sub file extentions each defined twice
in trunk mime.types:
.wmz: application/x-msmetafile, application/x-ms-wmz
.sub: text/vnd.dvb.subtitle, image/vnd.dvb.subtitle
Any ideas on which to keep? I'm happy to make the trivial commit,
but I don't follow
13 matches
Mail list logo