to cancel the incoming post data stream at an odd
point in time?
But I'm no expert, so I'm not sure at all.
Otto
On Wed, Apr 13, 2016 at 2:44 PM, Otto van der Schaaf <osch...@we-amp.com>
wrote:
> I'm pretty sure these logs correlate to the problems I am seeing, yes.
> Indeed the error
://gist.github.com/oschaaf/6396a614ce599d5003e50bb8e7106bed
Otto
On Wed, Apr 13, 2016 at 12:52 AM, Валентин Бартенев <vb...@nginx.com> wrote:
> On Wednesday 13 April 2016 00:08:43 Otto van der Schaaf wrote:
> > Hello,
> >
> > While looking into
> https://github.com/pagespe
Hello,
While looking into https://github.com/pagespeed/ngx_pagespeed/issues/1175 I
noticed that when performing a POST to a non-existing page, Chrome will
complain about the response (net::ERR_SPDY_PROTOCOL_ERROR).
This happens with a plain nginx build, configure arguments:
On Tue, Mar 24, 2015 at 6:01 PM, Maxim Dounin mdou...@mdounin.ru wrote:
If there are good reasons why the termination takes so long - we
may consider adding another iteration. Otherwise - yes, it'll
remain fixed.
I have a test to see if the module shuts down properly upon receiving
SIGTERM.
we need to be able to reliably test just this scenario,
so I've made a patch so we can run with different values for with and
without valgrind.
Would the following patch be acceptable?
Kind regards,
Otto
# HG changeset patch
# User Otto van der Schaaf osch...@we-amp.com
# Date 1427138606 -3600
? In
that case, we'll have a patch to maintain (or see if we can round up in
less time).
Thanks!
On Mon, Mar 23, 2015 at 11:18 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Mon, Mar 23, 2015 at 08:39:46PM +0100, Otto van der Schaaf wrote:
Hi,
For testing quick termination during
Hi,
For ngx_pagespeed, I'm looking for a way to persist its module request
context and restore it
even after request processing has been restarted for a named location or
internal redirect.
Keeping a single request context during this process would allow us to
avoid repeating some work we
