On Tue, Aug 19, 2014 at 9:04 AM, Eric Covener wrote:
> On Tue, Aug 19, 2014 at 8:59 AM, Jeff Trawick wrote:
> > I'm +0.75 or so for having to explicitly enable the use of CGIPassHeader
> in
> > htaccess.
>
> Is there an existing pattern for something to need to be explicitly
> named in AllowOver
On Tue, Aug 19, 2014 at 8:59 AM, Jeff Trawick wrote:
> I'm +0.75 or so for having to explicitly enable the use of CGIPassHeader in
> htaccess.
Is there an existing pattern for something to need to be explicitly
named in AllowOverrideList? But would that also basically guarantee
nobody who needs
On Mon, Aug 18, 2014 at 7:09 PM, Graham Dumpleton
wrote:
> The problem is sys admins who don't know what they are doing as far as
> administering Apache.
>
> I used to work in a corporate environment where they allowed everyone a
> ~username directory for placing stuff. As they wanted to allow pe
On Mon, Aug 18, 2014 at 7:22 PM, Graham Leggett wrote:
> On 16 Aug 2014, at 10:16 PM, Jeff Trawick wrote:
>
> > This core directive would be used to modify the processing of
> ap_add_common_vars() to pass through Authorization or Proxy-Authorization
> as HTTP_foo. (Nothing else is currently blo
@@ -3206,6 +3277,10 @@ static int event_pre_config(apr_pool_t *
"atomics not working as expected - add32 of negative
number");
return HTTP_INTERNAL_SERVER_ERROR;
}
+retained->idle_spawn_rate = apr_palloc(pconf, sizeof(int) *
num_buckets);
+
Hi,
i found the problematic lines of code.
The lua filename is merged with the LuaRoot-path, which not allowed to
be relative.
But the success of the merge is not checked.
mod_lua.c:194
if (filename) {
char *file;
apr_filepath_merge(&file, server_cfg->root_path,
