flood STATUS: -*-text-*-
Last modified at [$Date: 2003/07/01 20:55:12 $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13,
I checkout the cvs and got the lastest flood code, everything goes fine
untill the final make all is typed in. The error is
flood_net.c:81: warning: passing arg 4 of `apr_socket_create' makes
pointer from integer without a cast
flood_net.c:81: error: too many arguments to function
On Wed, 2004-02-04 at 19:41, André Malo wrote:
Anyone already working on switching to it?
I'm starting now with the code. Please speak up, if there's already work done.
AFAIK, noone is. Go for it.
Sander
When, with httpd-2.1, the pid file exists but has a zero size, then
httpd refuses to start.
The attached patch changes this behavior and removes the empty pid file
(but only if it exists AND is empty) and logs a message:
(17)File exists: Zero-length PID file logs/httpd.pid ignored.
to the
Let's do this in 2.1 by splitting out the file system,
and if the filesystem module isn't handling a request, it won't be serving
content but also won't be invoking the directory walk or stat-ing files.
this all sounds kinda interesting, and similar to the way auth has been set
up in 2.1 -
Yeah, it is a little weird, but not HTTP, another protocol on top of UDP
specific to our application.
MPM, so that section is the jumping-off point for considering UDP instead of
TCP, and the mod_echo for refernce to another protocol (though TCP) being
implemented in a module.
In fact, the
Thanks for the feedback, Will.
William A. Rowe, Jr. wrote:
At 03:39 PM 2/4/2004, [EMAIL PROTECTED] wrote:
But then if I play devil's advocate, someone could see the new directive and turn it on when it's not appropriate and cause Bad Things to happen. Mainly I'm looking for comments on whether
Joshua Slive wrote:
(without closer looking at the code)
I'd suggest rather
Location [virtual] /uri-path
/Location
where the virtual keyword defines that the location is independent from
filesystem.
Perhaps I'm misunderstanding the issue, but neither of these make sense to
me. It is not really
I just want to add a couple notes here on what I see as user-expectations.
The problem is that you want to add layers of additional directives, which
would change the behavior of Directory or Location ,
only Location , in a way that IMO is consistent with the existing
documentation, but
At 10:22 AM 2/5/2004, [EMAIL PROTECTED] wrote:
Thanks for the feedback, Will.
William A. Rowe, Jr. wrote:
At 03:39 PM 2/4/2004, [EMAIL PROTECTED] wrote:
But then if I play devil's advocate, someone could see the new directive
and turn it on when it's not appropriate and cause Bad Things to
I do, however, agree that doing a directory-walk on virtual resources is
not nice. But my opinion is that virtualness is a property of the
resource, and hence should be designated when selecting the resource.
That is why I suggested changing SetHandler rather than Location.
And perhaps I'm
Hi,
It's been a while since I played with the Apache code, and it'll be nice if
somebody can help me here.
I put some debug statements in the ssl_engine_io.c - in bio_filter_out_write() and
bio_filter_in_read() to see if the alert message is actually being sent, and got the
following
Jeff,
On Mon, 26 Jan 2004 Jeff Trawick wrote :
bug was that there were two places where we tried to close a single file
descriptor... 2nd close would fail with EBADF unless some other thread
had that file descriptor assigned to another file because it got a
socket or file or pipe or
This patch make it possible toreturn 304s when using the quick handler,
ifa fresh cache entity is found.
The r-mtime field is usually set in default_handler() (core.c) by calling
ap_update_mtime(), which does not happen when the quick handler
find a fresh cache entry.
At 10:43 AM 2/5/2004, Greg Marr wrote:
At 10:22 AM 2/5/2004, [EMAIL PROTECTED] wrote:
Thanks for the feedback, Will.
William A. Rowe, Jr. wrote:
At 03:39 PM 2/4/2004, [EMAIL PROTECTED] wrote:
But then if I play devil's advocate, someone could see the new directive and turn
it on when it's not
At 09:22 AM 2/5/2004, [EMAIL PROTECTED] wrote:
Effect/Issue 1:
Bypassing the filesystem canonicalization would be very bad on certain platforms
such as windows, depending on case sensitivity, etc. It would
also bypass *user configured* options such as avoiding symlinks.
only for Location If
I've seen some unclean shutdown errors a few times but never managed to
get a repro case. What client are you using, how do you reproduce this?
I presume you have the same SetEnvIf ssl-unclean-shutdown settings for
broken clients when comparing 1.3 and 2.0 behaviour?
On Thu, Feb 05, 2004 at
I tried using all the three 'unclean', 'standard' and 'accurate' shutdown methods. I'm
using MSIE 6.0 (and can attach the ssldump comparision for both Apache 1.3 and 2.x if
required)
As regards reproducing, I think you can reproduce it in any standard installation.
Here's a partial 'tusc'
Okay. here's what I think is happening : (Client = C Server - S)
C - S : initiates connection
C - S : handshake
S - C : server sends application data
S - C : server tries to read from the socket
- finds nothing (0 bytes returned)
- assumes transaction is completed, and
I bumped into a little strange side effect of autoconf with Apache 2.0.48. The
header file httpd.h includes ap_config.h, which in turn includes
ap_config_auto.h (on Unix/Linux). Now, this header, ap_config_auto.h has the
definitions of PACKAGE_NAME, PACKAGE_VERSION etc., presumably generated by
20 matches
Mail list logo
