I don't think this should be a discussion of whether chroot is worth
using as a security measure. IMHO it should be about allowing Apache
users to make a choice whether they will use chroot in this way or
not. I am usually an advocate for user choice. For example, I am well
aware of the various
On Jan 25, 2008 5:28 PM, Chris H. [EMAIL PROTECTED] wrote:
Greetings all,
I'm toying with the idea of using PCRE in Apache 1.3.
I see already that there is support for REGEX in the
Configuration.tmpl that permits a choice of bundled
or system (if available). But was wondering how hard,
or if
* Akins, Brian wrote:
On 1/25/08 3:51 PM, André Malo [EMAIL PROTECTED] wrote:
I don't recommend doing that as it contains a race condition (the file
might be changed in the meantime).
That race is in the default_handler as well, isn't it?
Yes. IIRC there's already a bug report for it.
On 1/25/08 3:51 PM, André Malo [EMAIL PROTECTED] wrote:
I don't recommend doing that as it contains a race condition (the file might
be changed in the meantime).
That race is in the default_handler as well, isn't it? It creates a file
bucket based on the size of an earlier stat. So, we are
On Fri 25 Jan 2008, Nick Kew wrote:
A
compromise might be to create a chroot hook and allow module
developers to use it. This would shift the support burden somewhat
from the core Apache team to those willing to engage the users
providing support.
Isn't that basically the status quo
* Akins, Brian wrote:
On 1/25/08 3:33 PM, André Malo [EMAIL PROTECTED] wrote:
If it should not
be chunked, the backend simply has to provide a content-length along
with the x-sendfile header.
Okay, I add ap_set_content_length(r, sub-finfo.size) and that fixes
it and does not chunk.
I
On 1/25/08 3:33 PM, André Malo [EMAIL PROTECTED] wrote:
If it should not
be chunked, the backend simply has to provide a content-length along with
the x-sendfile header.
Okay, I add ap_set_content_length(r, sub-finfo.size) and that fixes it
and does not chunk.
--
Brian Akins
Chief
On 1/25/08 3:33 PM, André Malo [EMAIL PROTECTED] wrote:
I'm not sure if a filter is semantically the right place. IMHO that smells a
bit problematic. It might be better to I'd rather hack that into a function
similar to ap_internal_redirect and let it call explicitly. That way you'd
need to
* Akins, Brian wrote:
I started to play with xsendfile more. I noticed the mod_xsendfile
floating around tried to basically replace what the default handler does
very well.
Basically, my version does a subrequest for the file. This allows things
like Deny from all, etc, to work. This
On 1/24/08 3:14 PM, Olaf van der Spek [EMAIL PROTECTED] wrote:
Working on making a FastCGI based setup the recommended approach
instead of mod_php is probably more important then async. Actually,
it's a prerequisite.
Fastcgi is the recommended way of using php and httpd 2, AFAIK. Isn't it???
On Fri, 25 Jan 2008 11:31:32 +
Ivan Ristic [EMAIL PROTECTED] wrote:
I don't think this should be a discussion of whether chroot is worth
using as a security measure. IMHO it should be about allowing Apache
users to make a choice whether they will use chroot in this way or
not.
+1.
For
Greetings all,
I'm toying with the idea of using PCRE in Apache 1.3.
I see already that there is support for REGEX in the
Configuration.tmpl that permits a choice of bundled
or system (if available). But was wondering how hard,
or if even reasonable to consider adding the same option
to use
I started to play with xsendfile more. I noticed the mod_xsendfile floating
around tried to basically replace what the default handler does very well.
Basically, my version does a subrequest for the file. This allows things
like Deny from all, etc, to work. This should be more secure, ie, if
13 matches
Mail list logo
