Where is the URL for the API's on Apache2. I can't seem to find a full
explanations for the Apache2 API. I got this link but it is all for
Apache1.X http://www.kuzbass.ru/docs/apache_c_mod_perl/1.htm
The API reference there is what I like to work with...
-Original Message-
From: Tikka,
On Fri, 27 Jun 2003, kibble wrote:
Where is the URL for the API's on Apache2. I can't seem to find a full
explanations for the Apache2 API. I got this link but it is all for
Apache1.X http://www.kuzbass.ru/docs/apache_c_mod_perl/1.htm
The API reference there is what I like to work with...
Mark J Cox wrote:
For those who wonder why Redhat didn't update Apache 2.0 in distro
8.0 and 9.0, just read :
http://www.redhat.com/advice/speaks_backport.html
Apache httpd was an example that I happened to remember when writing that
explanation - Apache is far from the worst offender to mix
On Wed, 25 Jun 2003, Glenn wrote:
Ok. I can accept that, even though we're talking the default config
for new installations. Security is my top priority and the Apache
configuration is _very_ flexible and likewise _very_ complex. Until
I slowly learned the Apache directives one by one and
Hello,
Just to add to this discussion--
It would be great to have a configuration directive to separate out stderr
messages from messages generated by Apache modules. It's often desirable
to parse error logs to generate statistics on 404s, etc. and stderr output
makes this more difficult.
This
On Fri, 27 Jun 2003, Andrew Ho wrote:
It would be great to have a configuration directive to separate out stderr
messages from messages generated by Apache modules. It's often desirable
to parse error logs to generate statistics on 404s, etc. and stderr output
makes this more difficult.
I
On Fri, Jun 27, 2003 at 07:21:09PM -0700, Andrew Ho wrote:
It would be great to have a configuration directive to separate out stderr
messages from messages generated by Apache modules. It's often desirable
to parse error logs to generate statistics on 404s, etc. and stderr output
makes this
I'm a member of the metacompilation research group at Stanford
(http://www.stanford.edu/~engler). We have a suite of checkers that
find bugs at compile time, and we've had quite a bit of success checking
the Linux kernel code for errors. Since our checkers can emit false
alarms, we filter the
I'm a member of the metacompilation research group at Stanford
(http://www.stanford.edu/~engler). We have a suite of checkers that
find bugs at compile time, and we've had quite a bit of success checking
the Linux kernel code for errors. Since our checkers can emit false
alarms, we filter the
At 06:47 AM 6/27/2003, Mark J Cox wrote:
For those who wonder why Redhat didn't update Apache 2.0 in distro
8.0 and 9.0, just read :
http://www.redhat.com/advice/speaks_backport.html
Apache httpd was an example that I happened to remember when writing that
explanation - Apache is far from
For those who wonder why Redhat didn't update Apache 2.0 in distro
8.0 and 9.0, just read :
http://www.redhat.com/advice/speaks_backport.html
For those who wonder why Redhat didn't update Apache 2.0 in distro
8.0 and 9.0, just read :
http://www.redhat.com/advice/speaks_backport.html
Apache httpd was an example that I happened to remember when writing that
explanation - Apache is far from the worst offender to mix security
updates
On Tuesday, June 24, 2003, at 12:35 PM, Jeremy Brown wrote:
[...]
generators running FreeBSD 5.1
You might try other operating systems. I don't know how well FreeBSD
compares, but I have had good luck on both Solaris (x86) and Linux 2.4.
Are there any tips to get more throughput on flood?
Depends
13 matches
Mail list logo
