title: Are chunk extensions supported by HTTP/2, and if so, how?
body: <p><a href="https://www.rfc-editor.org/rfc/rfc7230#section-4.1" rel="nofollow noreferrer">RFC 7230 §4.1</a> defined &quot;chunk extensions&quot;, additional key-value pairs that can be sent along with chunk in an HTTP message encoded with <code>Transfer-Encoding: chunked</code>:</p>
  <blockquote>
  <p>The chunked encoding allows each chunk to include zero or more chunk extensions, immediately following the chunk-size, for the sake of supplying per-chunk metadata (such as a signature or hash), mid-message control information, or randomization of message body size.</p>
  </blockquote>
  <p><a href="https://www.rfc-editor.org/rfc/rfc7540" rel="nofollow noreferrer">HTTP/2</a> claims,</p>
  <blockquote>
  <p>HTTP/2 is intended to be as compatible as possible with current uses of HTTP.  This means that, from the application perspective, the features of the protocol are largely unchanged.  To achieve this, all request and response semantics are preserved, although the syntax of conveying those semantics has changed.</p>
  </blockquote>
  <p>In HTTP/2, the <code>DATA</code> frames are used to carry data, in chunks, instead of the <code>chunked</code> Transfer-Encoding:</p>
  <blockquote>
  <p>HTTP/2 uses DATA frames to carry message payloads.  The &quot;chunked&quot; transfer encoding defined in Section 4.1 of [RFC7230] MUST NOT be used in HTTP/2.</p>
  </blockquote>
  <p>but, AFAICT, <code>DATA</code> frames offer no support for chunk extensions, only an optional padding.</p>
  <p>In particular, how is an HTTP/1.1 to HTTP/2 proxy, receiving a request containing chunks bearing well-formed chunk-extensions supposed to translate those chunks to HTTP/2?</p>