W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Clarification on HTTP/1.1 Server Response to HTTP/2 Client Connection Preface

From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
Date: Wed, 27 Aug 2014 17:29:20 +0000
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A9EBC50@BGB01XUD1012.national.core.bbc.co.uk>

I am looking for clarification on the expected behaviour in the scenario where a HTTP/2 client incorrect attempts to establish a HTTP/2 connection over cleartext TCP with a HTTP/1.1 server or intermediary. In this scenario, the client's prior knowledge is incorrect and a connection preface is sent as the first interaction after TCP connection.

The specification states "The client connection preface is selected so that a large proportion of HTTP/1.1 or HTTP/1.0 servers and intermediaries do not attempt to process further frames.", however I am unclear on what Response should be issued to the client my scenario above. There appears to be fair arguments for returning either 400, 405 or 505 depending upon the implementation parsing of the Request line.

I understand the connection preface has been crafted in order to provide robust handling of several use cases; such that a range of response codes may be valid dependent upon situation, however may it be useful to expand the paragraph in Section 3.5 to capture this succinctly?

Received on Wednesday, 27 August 2014 17:29:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:10 UTC