> Am 23.01.2017 um 02:52 schrieb Noel Butler :
>
> On 20/01/2017 07:45, Jacob Champion wrote:
>
>> On 01/19/2017 12:52 PM, Noel Butler wrote:
>>> Frequent releases set off alarms in system admins minds, frequent
>>> releases give the view of unstable/unreliable software, and that is the
>>> larg
Am 22.01.2017 um 22:22 schrieb Yann Ylavic:
> Hi Stefan,
>
> On Sun, Jan 22, 2017 at 8:00 PM, Stefan Priebe - Profihost AG
> wrote:
>> Am 22.01.2017 um 18:02 schrieb Eric Covener:
>>> On Sun, Jan 22, 2017 at 11:21 AM, Stefan Priebe - Profihost AG
>>> wrote:
Hi Stefan,
no i was mis
On 01/21/2017 09:57 AM, Yann Ylavic wrote:
> Hi,
>
> On Sat, Jan 21, 2017 at 7:40 AM, wrote:
>> Author: jailletc36
>> Date: Sat Jan 21 06:40:23 2017
>> New Revision: 1779700
>>
>> URL: http://svn.apache.org/viewvc?rev=1779700&view=rev
>> Log:
>> Save a few bytes and a few cycles.
>>
>> Modifie
OK, I was thinking something like this, which tries to "compartmentalize"
it to where we actually create the CGI vars...
Anyone able to test?
diff --git a/modules/mappers/mod_actions.c b/modules/mappers/mod_actions.c
index 2a67a2742..efe22f814 100644
--- a/modules/mappers/mod_actions.c
+++ b/modu
> Am 22.01.2017 um 22:22 schrieb Yann Ylavic :
>
> @icing: Any special expectation in mod_h2 with regard to mpm workers
> threads' lifetime (or keepalive connections that should stay alive for
> the configured limit)?
> I see that beam buckets make use of thread local storage/keys for
> locking,
Am 23.01.2017 um 21:54 schrieb Stefan Eissing:
>
>> Am 22.01.2017 um 22:22 schrieb Yann Ylavic :
>>
>> @icing: Any special expectation in mod_h2 with regard to mpm workers
>> threads' lifetime (or keepalive connections that should stay alive for
>> the configured limit)?
>> I see that beam bucket
On 01/23/2017 09:05 AM, Jim Jagielski wrote:
OK, I was thinking something like this, which tries to "compartmentalize"
it to where we actually create the CGI vars...
Anyone able to test?
This patch doesn't seem to change anything in my limited tests so far.
Comments inline:
diff --git a/mo
Hi Stefan,
On Mon, Jan 23, 2017 at 9:54 PM, Stefan Eissing
wrote:
>
> I am not aware of any special expectations now. Almost all is triggered by
> (parent) pool cleanups and is therefore more deterministic than before. The
> only explicit destroy is done on finished streams and slave connection
On Mon, Jan 23, 2017 at 11:37 PM, Yann Ylavic wrote:
> Hi Stefan,
>
> On Mon, Jan 23, 2017 at 9:54 PM, Stefan Eissing
> wrote:
>>
>> I am not aware of any special expectations now. Almost all is triggered by
>> (parent) pool cleanups and is therefore more deterministic than before. The
>> only
On 01/06/2017 01:00 PM, Jacob Champion wrote:
Give it a try! With so many ways to configure, I expect *someone* will
run into a corner case I've missed.
Has anyone else been able to give this a shot? Yann found the MPM-DSO
corner case already. :)
If no one else is having any issues, I figure
Yeah, this was fast and dirty and really a concept...
I'm in Arlington VA for the next coupla of days and won't be able to get
another look until later.
Basically, the idea was to trigger when FCGI is in place... Maybe notes is
better than subprocess_env for that special knowledge.
> On Jan 23, 2017, at 4:35 PM, Jacob Champion wrote:
>
>
> What situations lead to CONTENT_TYPE being set to a PATH_INFO delimiter? I'm
> not sure what this is supposed to do.
>
The *idea* was to look for ".php" in the actual URL for example :)
G/M,
In function:
static const char *remoteip_enable_proxy_protocol(cmd_parms *cmd, void *config,
my 'compiler' reports line 389 mod_remoteip.c:
remoteip_addr_info **rem_list[len_list];
> ^
"not a valid 'const' expression" even tho 'len_list is de
On Sun, Jan 22, 2017 at 7:52 PM, Noel Butler wrote:
> Perhaps the only person who wont bend over and take it up the arse like
> some people here expect, if I have an opinion, i'll voice it
>
Noel, your immediately prior post was an interesting example, although I
fail
to see how that particular
14 matches
Mail list logo
