Script updating gh-pages from dd36a72. [ci skip]

http/max-header-list-size/draft-ietf-quic-http.html

@@ -377,7 +377,7 @@
 
   <meta name="dct.creator" content="Bishop, M., Ed." />
   <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-quic-http-latest" />
-  <meta name="dct.issued" scheme="ISO8601" content="2019-06-06" />
+  <meta name="dct.issued" scheme="ISO8601" content="2019-06-07" />
   <meta name="dct.abstract" content="The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment.  This document describes a mapping of HTTP semantics over QUIC.  This document also identifies HTTP/2 features that are subsumed by QUIC, and describes how HTTP/2 extensions can be ported to HTTP/3." />
   <meta name="description" content="The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment.  This document describes a mapping of HTTP semantics over QUIC.  This document also identifies HTTP/2 features that are subsumed by QUIC, and describes how HTTP/2 extensions can be ported to HTTP/3." />
 
@@ -398,10 +398,10 @@
 </tr>
 <tr>
 <td class="left">Intended status: Standards Track</td>
-<td class="right">June 06, 2019</td>
+<td class="right">June 07, 2019</td>
 </tr>
 <tr>
-<td class="left">Expires: December 8, 2019</td>
+<td class="left">Expires: December 9, 2019</td>
 <td class="right"></td>
 </tr>
 
@@ -421,7 +421,7 @@ <h1 id="rfc.status"><a href="#rfc.status">Status of This Memo</a></h1>
 <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF).  Note that other groups may also distribute working documents as Internet-Drafts.  The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.</p>
 <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time.  It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
-<p>This Internet-Draft will expire on December 8, 2019.</p>
+<p>This Internet-Draft will expire on December 9, 2019.</p>
 <h1 id="rfc.copyrightnotice"><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
 <p>Copyright (c) 2019 IETF Trust and the persons identified as the document authors.  All rights reserved.</p>
 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.  Please review these documents carefully, as they describe your rights and restrictions with respect to this document.  Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.</p>
@@ -781,7 +781,7 @@ <h3 id="rfc.section.4.1.1">
 <p id="rfc.section.4.1.1.p.2">Just as in previous versions of HTTP, header field names are strings of ASCII characters that are compared in a case-insensitive fashion.  Properties of HTTP header field names and values are discussed in more detail in Section 3.2 of <a href="#RFC7230" class="xref">[RFC7230]</a>, though the wire rendering in HTTP/3 differs.  As in HTTP/2, header field names MUST be converted to lowercase prior to their encoding.  A request or response containing uppercase header field names MUST be treated as malformed.</p>
 <p id="rfc.section.4.1.1.p.3">As in HTTP/2, HTTP/3 uses special pseudo-header fields beginning with the &#8216;:&#8217; character (ASCII 0x3a) to convey the target URI, the method of the request, and the status code for the response.  These pseudo-header fields are defined in Section 8.1.2.3 and 8.1.2.4 of <a href="#HTTP2" class="xref">[HTTP2]</a>. Pseudo-header fields are not HTTP header fields.  Endpoints MUST NOT generate pseudo-header fields other than those defined in <a href="#HTTP2" class="xref">[HTTP2]</a>.  The restrictions on the use of pseudo-header fields in Section 8.1.2.1 of <a href="#HTTP2" class="xref">[HTTP2]</a> also apply to HTTP/3.</p>
 <p id="rfc.section.4.1.1.p.4">HTTP/3 uses QPACK header compression as described in <a href="#QPACK" class="xref">[QPACK]</a>, a variation of HPACK which allows the flexibility to avoid header-compression-induced head-of-line blocking.  See that document for additional details.</p>
-<p id="rfc.section.4.1.1.p.5">An HTTP/3 implementation MAY impose a limit on the maximum size of the header it will accept on an individual HTTP message; encountering a larger message header SHOULD be treated as a stream error of type <samp>HTTP_EXCESSIVE_LOAD</samp>.  The size of a header list is calculated based on the uncompressed size of header fields, including the length of the name and value in bytes plus an overhead of 32 bytes for each header field.</p>
+<p id="rfc.section.4.1.1.p.5">An HTTP/3 implementation MAY impose a limit on the maximum size of the header it will accept on an individual HTTP message.  A server that receives a larger header block than it is willing to handle can send an HTTP 431 (Request Header Fields Too Large) status code <a href="#RFC6585" class="xref">[RFC6585]</a>.  A client can discard responses that it cannot process.  The size of a header list is calculated based on the uncompressed size of header fields, including the length of the name and value in bytes plus an overhead of 32 bytes for each header field.</p>
 <p id="rfc.section.4.1.1.p.6">If an implementation wishes to advise its peer of this limit, it can be conveyed as a number of bytes in the <samp>SETTINGS_MAX_HEADER_LIST_SIZE</samp> parameter. An implementation which has received this parameter SHOULD NOT send an HTTP message header which exceeds the indicated size, as this will likely produce an error and could disrupt the entire connection if the peer reacts negatively.</p>
 <h3 id="rfc.section.4.1.2">
 <a href="#rfc.section.4.1.2">4.1.2.</a> <a href="#request-cancellation" id="request-cancellation">Request Cancellation and Rejection</a>
@@ -1909,6 +1909,11 @@ <h2 id="rfc.references.2">
 <a>Fielding, R.</a> and <a>J. Reschke</a>, "<a href="https://tools.ietf.org/html/rfc7231">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>", RFC 7231, DOI 10.17487/RFC7231, June 2014.</td>
 </tr>
 <tr>
+<td class="reference"><b id="RFC6585">[RFC6585]</b></td>
+<td class="top">
+<a>Nottingham, M.</a> and <a>R. Fielding</a>, "<a href="https://tools.ietf.org/html/rfc6585">Additional HTTP Status Codes</a>", RFC 6585, DOI 10.17487/RFC6585, April 2012.</td>
+</tr>
+<tr>
 <td class="reference"><b id="RFC7301">[RFC7301]</b></td>
 <td class="top">
 <a>Friedl, S.</a>, <a>Popov, A.</a>, <a>Langley, A.</a> and <a>E. Stephan</a>, "<a href="https://tools.ietf.org/html/rfc7301">Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension</a>", RFC 7301, DOI 10.17487/RFC7301, July 2014.</td>