Profihost, where bugs come to die!
I am currently fully overloaded, but it would be interesting to check how the
previous versions of the patch fare in a h2fuzz setup.
-Stefan
> Am 22.07.2017 um 02:18 schrieb Yann Ylavic :
>
> On Fri, Jul 21, 2017 at 10:31 PM, Stefan Priebe - Profihost AG
> w
On Fri, Jul 21, 2017 at 10:31 PM, Stefan Priebe - Profihost AG
wrote:
>
> your new defer linger V3 deadlocked as well.
>
> GDB traces:
> https://www.apaste.info/LMfJ
This shows the listener thread waiting for a worker while there are
many available.
My mistake, the worker threads failed to rearm
Hello Yann,
your new defer linger V3 deadlocked as well.
GDB traces:
https://www.apaste.info/LMfJ
But this time i have no fullstatus for you as the apache didn't serve
any connections at all anymore. But even before i did NOT see those
strange values for closing connections.
Thanks!
Greets,
St
This worked for me:
https://codeforgeek.com/2015/12/reverse-proxy-using-expressjs/
On 21 Jul 2017 9:32 PM, "Helmut K. C. Tessarek"
wrote:
On 2017-07-21 15:28, Stefan Pernar wrote:
> Thanks everyone. Got it done with nodejs, express and http-proxy.
You know, it is utterly useless to say you have
On 2017-07-21 15:28, Stefan Pernar wrote:
> Thanks everyone. Got it done with nodejs, express and http-proxy.
You know, it is utterly useless to say you have fixed it without telling
people how you did it.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 2
Thanks everyone. Got it done with nodejs, express and http-proxy.
Cheers
On 21 Jul 2017 6:41 PM, "Yann Ylavic" wrote:
> On Fri, Jul 21, 2017 at 6:26 PM, Stefan Pernar
> wrote:
> > Good catch - unfortunately it is still not working...
>
> Please define not working...
>
> Regards,
> Yann.
>
Hello Yann,
i downloaded V3. Can't guarantee when i can test. May be today or on monday.
Greets,
Stefan
Am 21.07.2017 um 01:08 schrieb Yann Ylavic:
> On Thu, Jul 20, 2017 at 12:48 PM, Stefan Priebe - Profihost AG
> wrote:
>> V3 didn't help.
>
> I just posted a new patch in this thread, with a
On Fri, Jul 21, 2017 at 6:26 PM, Stefan Pernar wrote:
> Good catch - unfortunately it is still not working...
Please define not working...
Regards,
Yann.
Good catch - unfortunately it is still not working...
On Fri, Jul 21, 2017 at 6:23 PM, Rainer Canavan wrote:
> > [...] What am I doing wrong?
>
> [...]
> >
> > ProxyPass "http://127.0.0.1:3000/";
> > ProxyPassReverse "http://127.0.0.0:3000/";
> ^
> That s
> [...] What am I doing wrong?
[...]
>
> ProxyPass "http://127.0.0.1:3000/";
> ProxyPassReverse "http://127.0.0.0:3000/";
^
That should be a 127.0.0.1.
rainer
Hi everyone,
I am running a node.js app on port 3000 and am serving PHP on port 3001.
Now I am trying to use Apache reverse proxy with the following .conf but it
just does not work. What am I doing wrong?
Options Indexes MultiViews
Require all granted
LoadModule proxy_module libexec/apache2/mo
> So, should we favor the draining of defer_linger_chain as much workers
> as necessary like the current patch, or should we have as few workers
> as possible and not start new workers in loops with no effect on
> defer_linger_chain?
I think the fewer workers option could lead to hard to debug (fr
> Also, it seems that in the deferred lingering case we should probaly
> shorten the socket timeout before calling (and possibly blocking on)
> ap_start_lingering_close()'s hooks/flush, since we likely come from a
> time-up already...
+1
On Fri, Jul 21, 2017 at 3:07 PM, Luca Toscano wrote:
>>
>> To prevent starvation of deferred lingering closes, the listener may
>> create a worker at the of its loop, when/if the chain is (fully)
>> filled.
>
> IIUC the trick is to run "(have_idle_worker && push2worker(NULL) ==
> APR_SUCCESS)" tha
Hi Yann,
2017-07-21 1:05 GMT+02:00 Yann Ylavic :
> On Fri, Jul 14, 2017 at 9:52 PM, Yann Ylavic wrote:
> >
> > So overall, this patch may introduce the need for more workers than
> > before, what was (wrongly) done by the listener thread has to be done
> > somewhere anyway...
>
> That patch didn
2017-07-21 1:16 GMT+02:00 Yann Ylavic :
> On Fri, Jul 21, 2017 at 1:05 AM, Postmaster
> wrote:
> > This message was created automatically by mail delivery software. Your
> email message was not delivered as is to the intended recipients because
> malware was detected in one or more attachments in
16 matches
Mail list logo