id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	uname	nginx_version
959	Permit post before acking settings	swankjesse@…	Valentin Bartenev <vbart@…>	"This report is motivated by a discussion on the HTTP-WG mailing list.
[https://lists.w3.org/Archives/Public/ietf-http-wg/2016AprJun/0174.html]

In OkHttp we’re investigating a bug where nginx v1.9.15 sends us
REFUSED_STREAM when we send our HEADERS and DATA frames before acking the
server’s SETTINGS.
[https://github.com/square/okhttp/issues/2506]

The spec says not waiting is okay:

> To avoid unnecessary latency, clients are permitted to send additional
> frames to the server immediately after sending the client connection
> preface, without waiting to receive the server connection preface. It is
> important to note, however, that the server connection preface SETTINGS
> frame might include parameters that necessarily alter how a client is
> expected to communicate with the server. Upon receiving the SETTINGS frame,
> the client is expected to honor any parameters established.

Not acking settings should not be the basis for refusing streams. This may
add significant latency to the initial HTTP request.

Please change nginx to accept streams created prior to the SETTINGS ack."	enhancement	closed	minor		nginx-core	1.9.x	fixed			Darwin jwilson.local 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016;	1.9.15