On Sun, 28 Dec 2003, bruce wrote:
basically, we need to be able to install a small apache footprint on a
Check out the (dynamic) modules and/or a static compile using hte
confoigure API (do a ./configure --help for a list). You can strip it down
very very far.
number of servers. we'd like
One of the problems that crops up depressingly often is that someone
gets owned, and they can't find out why. This is generally because the
offending request didn't get logged, because the server died before it
logged it.
So, I've written a forensic logging module. What this does is log the
Ben Laurie wrote:
One of the problems that crops up depressingly often is that someone
gets owned, and they can't find out why. This is generally because the
offending request didn't get logged, because the server died before it
logged it.
far more often than getting owned are the
Jeff Trawick wrote:
Ben Laurie wrote:
One of the problems that crops up depressingly often is that someone
gets owned, and they can't find out why. This is generally because the
offending request didn't get logged, because the server died before it
logged it.
far more often than getting
Ben Laurie wrote:
Jeff Trawick wrote:
Ben Laurie wrote:
One of the problems that crops up depressingly often is that someone
gets owned, and they can't find out why. This is generally because
the offending request didn't get logged, because the server died
before it logged it.
far more
On Mon, Dec 29, 2003 at 07:57:09PM +, Ben Laurie wrote:
Jeff Trawick wrote:
+1 (concept)
Excellent, do I hear more?
fwiw +1 from me too. This is a valuable module, and I can't see any harm
in making it available.
I think you should have to specify a log file name for it to do
Ben Laurie wrote:
If it does nothing unless a file is specified, why not enable by default?
to avoid silent growth in the set of code built into somebody's server... when
does somebody have to add --disable-foo to create a build compatible with
what they had with the 1.3.(n-1) release?
(I
On Mon, Dec 29, 2003 at 01:39:28PM +, Ben Laurie wrote:
So, I've written a forensic logging module. What this does is log the
request as soon as all the headers have been read, then log again when
its complete. Any request that doesn't complete should be viewed with
great suspicion!
On Thu, Dec 11, 2003 at 11:25:08AM +0200, Nasko wrote:
2) How can I be notified when a thread is destroyed so I can close the DB
connection
I think the correct way to do this would be to start a database thread
in child_init and register a thread shutdown callback with the pool
that is
On Thu, Dec 11, 2003 at 10:38:06AM -0800, Stas Bekman wrote:
What's confusing is that it seems that most consumers (not filters) (e.g. in
protocol.c) that call ap_pass_brigade are completely ignoring its response
code.
It seems to me that many output filters are also ignoring
ap_pass_brigade
Finally I've found some time to bring our build tools
(site-tools/httpd-docs-build) up to date.
Please update your checkout (takes a while) and post any errors here.
Thanks, nd
On Mon, 2003-12-29 at 20:57, Ben Laurie wrote:
Jeff Trawick wrote:
I propose that we should include this as a standard module.
+1 (concept)
Excellent, do I hear more?
Yes, +1 (concept). Actually, I'm in full agreement with Jeff on all
points ;).
Sander
Hi,
I am trying to use the function apr_table_setn for redirecting to a URL.
The following is the function call that I am using.
apr_table_setn( m_pReqRec-headers_out, (const char *)Location,
apr_pstrdup(m_pReqRec-pool, URL ));
But somehow I am not properly getting redirected. What I am
13 matches
Mail list logo
