+1 (plus after all this is done, a ap_mmn.h bump to accommodate
all the struct changes).
> On Feb 15, 2018, at 8:16 AM, Stefan Eissing
> wrote:
>
> Yep, that's it. Should listen to you more... :)
>
> I think we need that backported than, right?
>
>> Am 15.02.2018 um 14:11 schrieb Yann Ylavic
On Thu, Feb 15, 2018 at 2:16 PM, Stefan Eissing
wrote:
> Yep, that's it. Should listen to you more... :)
>
> I think we need that backported than, right?
+1
Yep, that's it. Should listen to you more... :)
I think we need that backported than, right?
> Am 15.02.2018 um 14:11 schrieb Yann Ylavic :
>
> On Thu, Feb 15, 2018 at 2:03 PM, Stefan Eissing
> wrote:
>> On my MacOS:
>>
>> r1824180 of mod_slotmem_shm.c exhibits the problem described
>> r182417
On Thu, Feb 15, 2018 at 2:03 PM, Stefan Eissing
wrote:
> On my MacOS:
>
> r1824180 of mod_slotmem_shm.c exhibits the problem described
> r1824179 of mod_slotmem_shm.c works
>
> This is really strange since r1824180 in 2.4.x is identical trunk, afaict.
>
> Tried restarting server, manually deleting
On my MacOS:
r1824180 of mod_slotmem_shm.c exhibits the problem described
r1824179 of mod_slotmem_shm.c works
This is really strange since r1824180 in 2.4.x is identical trunk, afaict.
Tried restarting server, manually deleting the slotmem files, rebooting
the machine, all the same.
Anyone a gu
On Wed, Feb 14, 2018 at 6:08 PM, Stefan Eissing
wrote:
>
> This looks not right, certainly? Seems like the balancer hook is not invoked
> on the request. But later on connection release, it is?
Different PIDs, the error is in the main server while hcheck
(watchdog) is running.
>
> Not really th
Adding
Index: modules/proxy/mod_proxy_balancer.c
===
--- modules/proxy/mod_proxy_balancer.c (revision 1824256)
+++ modules/proxy/mod_proxy_balancer.c (working copy)
@@ -1117,6 +1117,7 @@
const char *action;
apr_status_t rv;
On Wed, Feb 14, 2018 at 5:16 PM, Stefan Eissing
wrote:
> In my h2 test suite, I get on the 2.4.x branch a no longer working propxy
> setup.
>
> error_log shows
> [Wed Feb 14 17:11:35.996712 2018] [proxy:warn] [pid 69638:tid
> 123145425334272] [client 127.0.0.1:50616] AH01144: No protocol handler
balancer is loaded and has the same creation times than the others in my
modules directory. hmm...
> Am 14.02.2018 um 17:19 schrieb Graham Leggett :
>
> On 14 Feb 2018, at 6:16 PM, Stefan Eissing
> wrote:
>
>> In my h2 test suite, I get on the 2.4.x branch a no longer working propxy
>> setup
On 14 Feb 2018, at 6:16 PM, Stefan Eissing wrote:
> In my h2 test suite, I get on the 2.4.x branch a no longer working propxy
> setup.
>
> error_log shows
> [Wed Feb 14 17:11:35.996712 2018] [proxy:warn] [pid 69638:tid
> 123145425334272] [client 127.0.0.1:50616] AH01144: No protocol handler wa
In my h2 test suite, I get on the 2.4.x branch a no longer working propxy setup.
error_log shows
[Wed Feb 14 17:11:35.996712 2018] [proxy:warn] [pid 69638:tid 123145425334272]
[client 127.0.0.1:50616] AH01144: No protocol handler was valid for the URL
/proxy/index.html (scheme 'balancer'). If yo
11 matches
Mail list logo