On Wednesday 13 April 2016 19:35:25 Валентин Бартенев wrote:
> On Wednesday 13 April 2016 18:00:26 Валентин Бартенев wrote:
> > On Wednesday 13 April 2016 15:08:29 Otto van der Schaaf wrote:
> > > I'm sorry to say that the patch does not make a difference.
> > >
> > > I collected Chrome's http/2
On Wednesday 13 April 2016 18:00:26 Валентин Бартенев wrote:
> On Wednesday 13 April 2016 15:08:29 Otto van der Schaaf wrote:
> > I'm sorry to say that the patch does not make a difference.
> >
> > I collected Chrome's http/2 trace for a post to a non-existant url:
> >
On Wednesday 13 April 2016 15:08:29 Otto van der Schaaf wrote:
> I'm sorry to say that the patch does not make a difference.
>
> I collected Chrome's http/2 trace for a post to a non-existant url:
> https://gist.github.com/oschaaf/da273f96fad5e22890981fcd4a1a4376
>
> I'm wondering about that
I'm sorry to say that the patch does not make a difference.
I collected Chrome's http/2 trace for a post to a non-existant url:
https://gist.github.com/oschaaf/da273f96fad5e22890981fcd4a1a4376
I'm wondering about that last HTTP2_SESSION_RST_STREAM entry.. it looks
like
the httpv2 mod wants to
On Wednesday 13 April 2016 15:30:39 Валентин Бартенев wrote:
> On Wednesday 13 April 2016 13:54:24 Otto van der Schaaf wrote:
> > 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
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:
