Cowboy 2.6.2

12 files changed, 53 insertions, 15 deletions

diff --git a/docs/en/cowboy/2.6/guide/getting_started.asciidoc b/docs/en/cowboy/2.6/guide/getting_started.asciidoc
index 3215fb9c..97f2b205 100644
--- a/docs/en/cowboy/2.6/guide/getting_started.asciidoc
+++ b/docs/en/cowboy/2.6/guide/getting_started.asciidoc
@@ -69,7 +69,7 @@ fetch and compile Cowboy:
 PROJECT = hello_erlang
 
 DEPS = cowboy
-dep_cowboy_commit = 2.6.1
+dep_cowboy_commit = 2.6.2
 
 DEP_PLUGINS = cowboy
 
diff --git a/docs/en/cowboy/2.6/guide/getting_started/index.html b/docs/en/cowboy/2.6/guide/getting_started/index.html
index beda3c89..75787e02 100644
--- a/docs/en/cowboy/2.6/guide/getting_started/index.html
+++ b/docs/en/cowboy/2.6/guide/getting_started/index.html
@@ -109,7 +109,7 @@ http://www.gnu.org/software/src-highlite -->
 <pre><tt><font color="#009900">PROJECT =</font> hello_erlang
 
 <font color="#009900">DEPS =</font> cowboy
-<font color="#009900">dep_cowboy_commit =</font> 2.6.1
+<font color="#009900">dep_cowboy_commit =</font> 2.6.2
 
 <font color="#009900">DEP_PLUGINS =</font> cowboy
 
diff --git a/docs/en/cowboy/2.6/guide/migrating_from_2.6.asciidoc b/docs/en/cowboy/2.6/guide/migrating_from_2.6.asciidoc
index 0adab3e9..14ce5d5a 100644
--- a/docs/en/cowboy/2.6/guide/migrating_from_2.6.asciidoc
+++ b/docs/en/cowboy/2.6/guide/migrating_from_2.6.asciidoc
@@ -3,6 +3,29 @@
 
 The following patch versions were released since Cowboy 2.6:
 
+=== Cowboy 2.6.2
+
+This release updates Cowlib to 2.7.2.
+
+A bug in the HTTP/2 code that resulted in the failure to
+fully send iolist response bodies has been fixed. Cowboy
+would just wait indefinitely in those cases.
+
+Cowboy will now use the host header when the HTTP/2
+:authority pseudo header is missing. A common scenario
+where this occurs is when proxies translate incoming
+HTTP/1.1 requests to HTTP/2.
+
+The `cowboy_static` handler will now properly detect
+the type of files that have an uppercase or mixed
+extension component.
+
+A bug where the stacktrace was incorrect in error messages
+has been fixed. The problem occurred when an exception
+occurred in the handler's terminate callback.
+
+Minor documentation fixes.
+
 === Cowboy 2.6.1
 
 This release updates Ranch to 1.7.1.
diff --git a/docs/en/cowboy/2.6/guide/migrating_from_2.6/index.html b/docs/en/cowboy/2.6/guide/migrating_from_2.6/index.html
index a50561cd..aa293d5c 100644
--- a/docs/en/cowboy/2.6/guide/migrating_from_2.6/index.html
+++ b/docs/en/cowboy/2.6/guide/migrating_from_2.6/index.html
@@ -63,6 +63,13 @@
 <h1 class="lined-header"><span>Changes since Cowboy 2.6</span></h1>
 
 <p>The following patch versions were released since Cowboy 2.6:</p>
+<h2 id="_cowboy_2_6_2">Cowboy 2.6.2</h2>
+<p>This release updates Cowlib to 2.7.2.</p>
+<p>A bug in the HTTP/2 code that resulted in the failure to fully send iolist response bodies has been fixed. Cowboy would just wait indefinitely in those cases.</p>
+<p>Cowboy will now use the host header when the HTTP/2 :authority pseudo header is missing. A common scenario where this occurs is when proxies translate incoming HTTP/1.1 requests to HTTP/2.</p>
+<p>The <code>cowboy_static</code> handler will now properly detect the type of files that have an uppercase or mixed extension component.</p>
+<p>A bug where the stacktrace was incorrect in error messages has been fixed. The problem occurred when an exception occurred in the handler&apos;s terminate callback.</p>
+<p>Minor documentation fixes.</p>
 <h2 id="_cowboy_2_6_1">Cowboy 2.6.1</h2>
 <p>This release updates Ranch to 1.7.1.</p>
 <p>It fixes an issue with the PROXY protocol where the wrong CRC32 algorithm was used and would cause checksum verification to fail.</p>
diff --git a/docs/en/cowboy/2.6/guide/rest_flowcharts.asciidoc b/docs/en/cowboy/2.6/guide/rest_flowcharts.asciidoc
index b5697825..308a919e 100644
--- a/docs/en/cowboy/2.6/guide/rest_flowcharts.asciidoc
+++ b/docs/en/cowboy/2.6/guide/rest_flowcharts.asciidoc
@@ -16,7 +16,8 @@ exists.
 The red squares refer to another diagram. The light green squares
 indicate a response. Other squares may be either a callback or a
 question answered by Cowboy itself. Green arrows tend to indicate
-the default behavior if the callback is undefined.
+the default behavior if the callback is undefined. The star next
+to values indicate that the value is descriptive rather than exact.
 
 === Start
 
diff --git a/docs/en/cowboy/2.6/guide/rest_flowcharts/index.html b/docs/en/cowboy/2.6/guide/rest_flowcharts/index.html
index b1c6dc2c..5bd60360 100644
--- a/docs/en/cowboy/2.6/guide/rest_flowcharts/index.html
+++ b/docs/en/cowboy/2.6/guide/rest_flowcharts/index.html
@@ -65,7 +65,7 @@
 <p>This chapter will explain the REST handler state machine through a number of different diagrams.</p>
 <p>There are four main paths that requests may follow. One for the method OPTIONS; one for the methods GET and HEAD; one for the methods PUT, POST and PATCH; and one for the method DELETE.</p>
 <p>All paths start with the &quot;Start&quot; diagram, and all paths excluding the OPTIONS path go through the &quot;Content negotiation&quot; diagram and optionally the &quot;Conditional requests&quot; diagram if the resource exists.</p>
-<p>The red squares refer to another diagram. The light green squares indicate a response. Other squares may be either a callback or a question answered by Cowboy itself. Green arrows tend to indicate the default behavior if the callback is undefined.</p>
+<p>The red squares refer to another diagram. The light green squares indicate a response. Other squares may be either a callback or a question answered by Cowboy itself. Green arrows tend to indicate the default behavior if the callback is undefined. The star next to values indicate that the value is descriptive rather than exact.</p>
 <h2 id="_start">Start</h2>
 <p>All requests start from here.</p>
 <img src="../rest_start.png" alt="REST starting flowchart"/><p>A series of callbacks are called in succession to perform a general checkup of the service, the request line and request headers.</p>
diff --git a/docs/en/cowboy/2.6/guide/specs.asciidoc b/docs/en/cowboy/2.6/guide/specs.asciidoc
index fa76793f..06751cd5 100644
--- a/docs/en/cowboy/2.6/guide/specs.asciidoc
+++ b/docs/en/cowboy/2.6/guide/specs.asciidoc
@@ -149,6 +149,7 @@ for or related to HTTP.
 * https://tools.ietf.org/html/rfc2965[RFC 2965]: HTTP State Management Mechanism (Cookie2)
 * https://tools.ietf.org/html/rfc3229[RFC 3229]: Delta encoding in HTTP
 * https://tools.ietf.org/html/rfc7168[RFC 7168]: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
+* https://tools.ietf.org/html/rfc8565[RFC 8565]: Hypertext Jeopardy Protocol (HTJP/1.0)
 * http://dev.chromium.org/spdy/spdy-protocol[SPDY]: SPDY Protocol
 * https://tools.ietf.org/html/draft-tyoshino-hybi-websocket-perframe-deflate-06[x-webkit-deflate-frame]: Deprecated Websocket compression
 
@@ -196,3 +197,4 @@ for or related to HTTP.
 * https://tools.ietf.org/html/rfc8075[RFC 8075]: Guidelines for Mapping Implementations: HTTP to CoAP
 * https://tools.ietf.org/html/rfc8132[RFC 8132]: PATCH and FETCH Methods for CoAP
 * https://tools.ietf.org/html/rfc8323[RFC 8323]: CoAP over TCP, TLS, and WebSockets
+* https://tools.ietf.org/html/rfc8516[RFC 8516]: "Too Many Requests" Response Code for CoAP
diff --git a/docs/en/cowboy/2.6/guide/specs/index.html b/docs/en/cowboy/2.6/guide/specs/index.html
index b6ff9e49..e113ef95 100644
--- a/docs/en/cowboy/2.6/guide/specs/index.html
+++ b/docs/en/cowboy/2.6/guide/specs/index.html
@@ -327,6 +327,8 @@
 </li>
 <li><a href="https://tools.ietf.org/html/rfc7168">RFC 7168</a>: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
 </li>
+<li><a href="https://tools.ietf.org/html/rfc8565">RFC 8565</a>: Hypertext Jeopardy Protocol (HTJP/1.0)
+</li>
 <li><a href="http://dev.chromium.org/spdy/spdy-protocol">SPDY</a>: SPDY Protocol
 </li>
 <li><a href="https://tools.ietf.org/html/draft-tyoshino-hybi-websocket-perframe-deflate-06">x-webkit-deflate-frame</a>: Deprecated Websocket compression
@@ -409,6 +411,8 @@
 </li>
 <li><a href="https://tools.ietf.org/html/rfc8323">RFC 8323</a>: CoAP over TCP, TLS, and WebSockets
 </li>
+<li><a href="https://tools.ietf.org/html/rfc8516">RFC 8516</a>: &quot;Too Many Requests&quot; Response Code for CoAP
+</li>
 </ul>
 
 
diff --git a/docs/en/cowboy/2.6/guide/static_files.asciidoc b/docs/en/cowboy/2.6/guide/static_files.asciidoc
index 9d9b8cc2..5af911be 100644
--- a/docs/en/cowboy/2.6/guide/static_files.asciidoc
+++ b/docs/en/cowboy/2.6/guide/static_files.asciidoc
@@ -43,12 +43,12 @@ which means that your route must end with a `[...]` pattern
 for it to work. All files are served, including the ones that
 may be found in subfolders.
 
-You can specify the directory relative to an application's
-private directory.
+You can specify the directory relative to the application's
+private directory (e.g. `my_app/priv`).
 
-The following rule will serve any file found in the application
-`my_app`'s priv directory inside the `static/assets` folder
-whenever the requested path begins with `/assets/`:
+The following rule will serve any file found in the `my_app`
+application's private directory in the `my_app/priv/static/assets`
+folder whenever the requested path begins with `/assets/`:
 
 [source,erlang]
 {"/assets/[...]", cowboy_static, {priv_dir, my_app, "static/assets"}}
diff --git a/docs/en/cowboy/2.6/guide/static_files/index.html b/docs/en/cowboy/2.6/guide/static_files/index.html
index 1e351a40..4439e2c2 100644
--- a/docs/en/cowboy/2.6/guide/static_files/index.html
+++ b/docs/en/cowboy/2.6/guide/static_files/index.html
@@ -83,8 +83,8 @@ http://www.gnu.org/software/src-highlite -->
 </div></div>
 <h2 id="_serve_all_files_from_a_directory">Serve all files from a directory</h2>
 <p>You can also use the static handler to serve all files that can be found in the configured directory. The handler will use the <code>path_info</code> information to resolve the file location, which means that your route must end with a <code>[...]</code> pattern for it to work. All files are served, including the ones that may be found in subfolders.</p>
-<p>You can specify the directory relative to an application&apos;s private directory.</p>
-<p>The following rule will serve any file found in the application <code>my_app</code>&apos;s priv directory inside the <code>static/assets</code> folder whenever the requested path begins with <code>/assets/</code>:</p>
+<p>You can specify the directory relative to the application&apos;s private directory (e.g. <code>my_app/priv</code>).</p>
+<p>The following rule will serve any file found in the <code>my_app</code> application&apos;s private directory in the <code>my_app/priv/static/assets</code> folder whenever the requested path begins with <code>/assets/</code>:</p>
 <div class="listingblock"><div class="content"><!-- Generator: GNU source-highlight 3.1.8
 by Lorenzo Bettini
 http://www.lorenzobettini.it
diff --git a/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_cookie/index.html b/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_cookie/index.html
index a1b66c2e..f0d208ce 100644
--- a/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_cookie/index.html
+++ b/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_cookie/index.html
@@ -70,7 +70,7 @@ by Lorenzo Bettini
 http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->
 <pre><tt><b><font color="#000000">set_resp_cookie</font></b>(<font color="#009900">Name</font>, <font color="#009900">Value</font>, <font color="#009900">Req</font> <font color="#990000">::</font> <b><font color="#000000">cowboy_req:req</font></b>())
-    <font color="#990000">-&gt;</font> <b><font color="#000000">set_resp_cookie</font></b>(<font color="#009900">Name</font>, <font color="#009900">Value</font>, [], <font color="#009900">Req</font>)
+    <font color="#990000">-&gt;</font> <b><font color="#000000">set_resp_cookie</font></b>(<font color="#009900">Name</font>, <font color="#009900">Value</font>, <font color="#009900">Req</font>, #{})
 
 <b><font color="#000000">set_resp_cookie</font></b>(<font color="#009900">Name</font>, <font color="#009900">Value</font>, <font color="#009900">Req</font> <font color="#990000">::</font> <b><font color="#000000">cowboy_req:req</font></b>(), <font color="#009900">Opts</font>)
     <font color="#990000">-&gt;</font> <font color="#009900">Req</font>
diff --git a/docs/index.xml b/docs/index.xml
index 3b9d0e0e..2afce399 100644
--- a/docs/index.xml
+++ b/docs/index.xml
@@ -3182,8 +3182,9 @@ Cowboy 2.2.2 While fixing the miscount in the previous patch release an issue wa
       
       <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.6/</guid>
       <description>The following patch versions were released since Cowboy 2.6:
-Cowboy 2.6.1 This release updates Ranch to 1.7.1.
-It fixes an issue with the PROXY protocol where the wrong CRC32 algorithm was used and would cause checksum verification to fail.</description>
+Cowboy 2.6.2 This release updates Cowlib to 2.7.2.
+A bug in the HTTP/2 code that resulted in the failure to fully send iolist response bodies has been fixed. Cowboy would just wait indefinitely in those cases.
+Cowboy will now use the host header when the HTTP/2 :authority pseudo header is missing. A common scenario where this occurs is when proxies translate incoming HTTP/1.</description>
     </item>
     
     <item>
@@ -8582,7 +8583,7 @@ Arguments Name Cookie name.
       
       <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_cookie/</guid>
       <description>Name cowboy_req:set_resp_cookie - Set a cookie
-Description set_resp_cookie(Name, Value, Req :: cowboy_req:req()) -&amp;gt; set_resp_cookie(Name, Value, [], Req) set_resp_cookie(Name, Value, Req :: cowboy_req:req(), Opts) -&amp;gt; Req Name :: binary() %% case sensitive Value :: iodata() %% case sensitive Opts :: cow_cookie:cookie_opts()  Set a cookie to be sent with the response.
+Description set_resp_cookie(Name, Value, Req :: cowboy_req:req()) -&amp;gt; set_resp_cookie(Name, Value, Req, #{}) set_resp_cookie(Name, Value, Req :: cowboy_req:req(), Opts) -&amp;gt; Req Name :: binary() %% case sensitive Value :: iodata() %% case sensitive Opts :: cow_cookie:cookie_opts()  Set a cookie to be sent with the response.
 Note that cookie names are case sensitive.
 Arguments Name Cookie name.
  Value Cookie value.