1.9.14 - http2 protocol violations

[Otto van der Schaaf]

Sure.

- This sample contains to or three requests, the last request is where rate
limiting kicks in and the protocol error happens (the earlier requests are
problem-free):
 https://gist.github.com/oschaaf/281b7a0fed9954dd960adac55e96f2cd

- This is from a post to a non-existant url:
https://gist.github.com/oschaaf/6396a614ce599d5003e50bb8e7106bed

Otto

On Wed, Apr 13, 2016 at 12:52 AM, Валентин Бартенев <vbart at nginx.com> wrote:

> On Wednesday 13 April 2016 00:08:43 Otto van der Schaaf wrote:
> > 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:
> > --prefix=/home/oschaaf/nginx-tmpbuild --with-http_v2_module
> > --with-http_ssl_module
> >
> > 1.9.14 seems to have introduced some behavioral changes only noticable on
> > http2, there seem to be similar breakages in some of ngx_pagespeed's
> flows.
> >
> > One thing we do is perform an async lookup in the preaccess phase - doing
> > so when processing a POST request also results in a protocol violation.
> > As this path looks very similar to the limit request module, I tested
> that
> > as well. And indeed this also seems to give the same error on http/2
> >
> [..]
>
> Could you provide the debug log?
>
>   wbr, Valentin V. Bartenev
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20160413/f5d2e642/attachment.html>