W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2016

Post before acking settings?

From: Jesse Wilson <jesse@swank.ca>
Date: Wed, 27 Apr 2016 02:22:14 +0000
Message-ID: <CAME=j1kn9YthfEAMNVNEULy4tS7wHSgXTyR-08ZEOBqgczTD5g@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
In OkHttp we’re investigating a bug
<https://github.com/square/okhttp/issues/2506> where nginx v1.9.15 sends us
REFUSED_STREAM when we send our HEADERS and DATA frames before acking the
server’s SETTINGS.

Should a well behaved HTTP/2 client wait to ack the server’s SETTINGS
before sending other frames? 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.

I’d love advice on how to resolve this. My options as I see them:

   1. Change the client to ack SETTINGS before sending other frames.
   2. Petition HTTP/2 server implementors to not refuse streams that
   precede the SETTINGS ack.
   3. Recover when we get a REFUSED_STREAM.

Note that recovering from a REFUSED_STREAM isn’t an easy win for us. OkHttp
doesn’t retain the (potentially large, potentially sensitive) request body
bytes that were posted. To recover the application layer will be prompted
for new request body bytes. This is typically just serializing some JSON.
But it could be invasive, like prompting a user for their fingerprint so
that a device’s secure element can be used.

– Jesse
Received on Wednesday, 27 April 2016 02:22:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:51 UTC