Cowboy 2.12, Cowlib 2.13, Gun 2.1

1 files changed, 2256 insertions, 0 deletions

diff --git a/index.xml b/index.xml
index 6d006576..cdfc2358 100644
--- a/index.xml
+++ b/index.xml
@@ -88,6 +88,21 @@ Copyright (c) 2013-2023, Loïc Hoguin <[email protected]> Permiss
     
     <item>
       <title>Introduction</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/introduction/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/introduction/</guid>
+      <description>Gun is an HTTP client for Erlang/OTP.
+Gun supports the HTTP/2, HTTP/1.1 and Websocket protocols.
+Prerequisites Knowledge of Erlang, but also of the HTTP/1.1, HTTP/2 and Websocket protocols is required in order to read this guide.
+Supported platforms Gun is tested and supported on Linux, FreeBSD, Windows and OSX.
+Gun is developed for Erlang/OTP 22.0 and newer.
+License Gun uses the ISC License.
+Copyright (c) 2013-2023, Loïc Hoguin &amp;lt;[email protected]&amp;gt; Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.</description>
+    </item>
+    
+    <item>
+      <title>Introduction</title>
       <link>https://ninenines.eu/docs/en/ranch/1.6/guide/introduction/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -170,6 +185,17 @@ HTTP/2 HTTP/2 is the most efficient protocol for consuming Web services. It enab
     
     <item>
       <title>The modern Web</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/modern_web/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/modern_web/</guid>
+      <description>Cowboy is a server for the modern Web. This chapter explains what it means and details all the standards involved.
+Cowboy supports all the standards listed in this document.
+HTTP/2 HTTP/2 is the most efficient protocol for consuming Web services. It enables clients to keep a connection open for long periods of time; to send requests concurrently; to reduce the size of requests through HTTP headers compression; and more. The protocol is binary, greatly reducing the resources needed to parse it.</description>
+    </item>
+    
+    <item>
+      <title>The modern Web</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/modern_web/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -234,6 +260,16 @@ The Web is concurrent When you access a website there is little concurrency invo
     
     <item>
       <title>Erlang and the Web</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/erlang_web/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/erlang_web/</guid>
+      <description>Erlang is the ideal platform for writing Web applications. Its features are a perfect match for the requirements of modern Web applications.
+The Web is concurrent When you access a website there is little concurrency involved. A few connections are opened and requests are sent through these connections. Then the web page is displayed on your screen. Your browser will only open up to 4 or 8 connections to the server, depending on your settings.</description>
+    </item>
+    
+    <item>
+      <title>Erlang and the Web</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/erlang_web/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -383,6 +419,18 @@ Adding Gun as an Erlang.mk dependency source-highlight: could not find a languag
     </item>
     
     <item>
+      <title>Starting and stopping</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/start/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/start/</guid>
+      <description>This chapter describes how to start and stop the Gun application.
+Setting up Specify Gun as a dependency to your application in your favorite build tool.
+With Erlang.mk this is done by adding gun to the DEPS variable in your Makefile.
+Adding Gun as an Erlang.mk dependency source-highlight: could not find a language definition for make  Starting Gun is an OTP application. It needs to be started before you can use it.</description>
+    </item>
+    
+    <item>
       <title>Supported protocols</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/guide/protocols/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -443,6 +491,18 @@ Gun will send a gun_inform message for every intermediate informational response
     </item>
     
     <item>
+      <title>Supported protocols</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/protocols/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/protocols/</guid>
+      <description>This chapter describes the protocols supported and the operations available to them.
+HTTP/1.1 HTTP/1.1 is a text request-response protocol. The client sends a request, the server sends back a response.
+Gun provides convenience functions for performing GET, HEAD, OPTIONS, POST, PATCH, PUT, and DELETE requests. All these functions are aliases of gun:headers/4,5 or gun:request/5,6 for the respective methods. Gun also provides a gun:data/4 function for streaming the request body.
+Gun will send a gun_inform message for every intermediate informational responses received.</description>
+    </item>
+    
+    <item>
       <title>Introduction</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/guide/introduction/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -468,6 +528,18 @@ Cowboy is a high quality project. It has a small code base, is very efficient (b
     
     <item>
       <title>Introduction</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/introduction/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/introduction/</guid>
+      <description>Cowboy is a small, fast and modern HTTP server for Erlang/OTP.
+Cowboy aims to provide a complete modern Web stack. This includes HTTP/1.1, HTTP/2, Websocket, Server-Sent Events and Webmachine-based REST.
+Cowboy comes with functions for introspection and tracing, enabling developers to know precisely what is happening at any time. Its modular design also easily enable developers to add instrumentation.
+Cowboy is a high quality project. It has a small code base, is very efficient (both in latency and memory use) and can easily be embedded in another application.</description>
+    </item>
+    
+    <item>
+      <title>Introduction</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/introduction/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -635,6 +707,17 @@ A Gun connection is an Erlang process that manages a socket to a remote endpoint
     </item>
     
     <item>
+      <title>Connection</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/connect/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/connect/</guid>
+      <description>This chapter describes how to open, monitor and close a connection using the Gun client.
+Gun connections Gun is designed with the HTTP/2 and Websocket protocols in mind. They are built for long-running connections that allow concurrent exchange of data, either in the form of request/responses for HTTP/2 or in the form of messages for Websocket.
+A Gun connection is an Erlang process that manages a socket to a remote endpoint.</description>
+    </item>
+    
+    <item>
       <title>Protocols</title>
       <link>https://ninenines.eu/docs/en/ranch/1.6/guide/protocols/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -706,6 +789,16 @@ This chapter walks you through all the steps of setting up Cowboy, writing your
     
     <item>
       <title>Getting started</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/getting_started/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/getting_started/</guid>
+      <description>Erlang is more than a language, it is also an operating system for your applications. Erlang developers rarely write standalone modules, they write libraries or applications, and then bundle those into what is called a release. A release contains the Erlang VM plus all applications required to run the node, so it can be pushed to production directly.
+This chapter walks you through all the steps of setting up Cowboy, writing your first application and generating your first release.</description>
+    </item>
+    
+    <item>
+      <title>Getting started</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/getting_started/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -805,6 +898,18 @@ Streams can be canceled at any time.</description>
     </item>
     
     <item>
+      <title>HTTP</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/http/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/http/</guid>
+      <description>This chapter describes how to use the Gun client for communicating with an HTTP/1.1 or HTTP/2 server.
+Streams Every time a request is initiated, Gun creates a stream. A stream reference uniquely identifies a set of request and response and must be used to perform additional operations with a stream or to identify its messages.
+Stream references use the Erlang reference data type and are therefore unique.
+Streams can be canceled at any time.</description>
+    </item>
+    
+    <item>
       <title>Embedded mode</title>
       <link>https://ninenines.eu/docs/en/ranch/1.6/guide/embedded/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -880,6 +985,18 @@ After Ranch accepts a new connection, whether it is an HTTP/1.</description>
     
     <item>
       <title>Flow diagram</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/flow_diagram/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/flow_diagram/</guid>
+      <description>Cowboy is a lightweight HTTP server with support for HTTP/1.1, HTTP/2 and Websocket.
+It is built on top of Ranch. Please see the Ranch guide for more information about how the network connections are handled.
+Overview As you can see on the diagram, the client begins by connecting to the server. This step is handled by a Ranch acceptor, which is a process dedicated to accepting new connections.
+After Ranch accepts a new connection, whether it is an HTTP/1.</description>
+    </item>
+    
+    <item>
+      <title>Flow diagram</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/flow_diagram/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -982,6 +1099,17 @@ You must use the gun:ws_upgrade/2,3,4 function to upgrade to Websocket.</descrip
     </item>
     
     <item>
+      <title>Websocket</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/websocket/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/websocket/</guid>
+      <description>This chapter describes how to use the Gun client for communicating with a Websocket server.
+HTTP upgrade Websocket is a protocol built on top of HTTP. To use Websocket, you must first request for the connection to be upgraded. Only HTTP/1.1 connections can be upgraded to Websocket, so you might need to restrict the protocol to HTTP/1.1 if you are planning to use Websocket over TLS.
+You must use the gun:ws_upgrade/2,3,4 function to upgrade to Websocket.</description>
+    </item>
+    
+    <item>
       <title>Writing parsers</title>
       <link>https://ninenines.eu/docs/en/ranch/1.6/guide/parsers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1058,6 +1186,16 @@ In order to have a TLS layer inside another TLS layer we need a way to encode th
     </item>
     
     <item>
+      <title>Internals: TLS over TLS</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/internals_tls_over_tls/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/internals_tls_over_tls/</guid>
+      <description>The ssl application that comes with Erlang/OTP implements TLS using an interface equivalent to the gen_tcp interface: you get and manipulate a socket. The TLS encoding and decoding is applied transparently to the data sent and received.
+In order to have a TLS layer inside another TLS layer we need a way to encode the data of the inner layer before we pass it to the outer layer. We cannot do this with a socket interface.</description>
+    </item>
+    
+    <item>
       <title>Migrating from Gun 1.0 to 1.1</title>
       <link>https://ninenines.eu/docs/en/gun/1.1/guide/migrating_from_1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1101,6 +1239,17 @@ Cowboy provides two types of listeners: one listening for clear TCP connections,
     
     <item>
       <title>Listeners</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/listeners/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/listeners/</guid>
+      <description>A listener is a set of processes that listens on a port for new connections. Incoming connections get handled by Cowboy. Depending on the connection handshake, one or another protocol may be used.
+This chapter is specific to Cowboy. Please refer to the Ranch User Guide for more information about listeners.
+Cowboy provides two types of listeners: one listening for clear TCP connections, and one listening for secure TLS connections. Both of them support the HTTP/1.</description>
+    </item>
+    
+    <item>
+      <title>Listeners</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/listeners/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -1219,6 +1368,18 @@ If no configured host matches the request URI, a 400 response is returned.  Othe
     
     <item>
       <title>Routing</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/routing/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/routing/</guid>
+      <description>Cowboy does nothing by default.
+To make Cowboy useful, you need to map URIs to Erlang modules that will handle the requests. This is called routing.
+Cowboy routes requests using the following algorithm:
+If no configured host matches the request URI, a 400 response is returned.  Otherwise, the first configured host that matches the request URI will be used. Only the paths configured for this host will be considered.  If none of the configured paths found in the previous step match the request URI, a 404 response is returned.</description>
+    </item>
+    
+    <item>
+      <title>Routing</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/routing/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -1347,6 +1508,17 @@ It also fixes parsing of RST_STREAM frames to properly handle frames that have a
     </item>
     
     <item>
+      <title>Migrating from Gun 2.0 to 2.1</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_2.0/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_2.0/</guid>
+      <description>Gun 2.1 contains a small security improvement for the HTTP/2 protocol, as well as includes a small number of fixes and improvements.
+Gun 2.1 requires Erlang/OTP 22.0 or greater.
+Features added A new HTTP/2 option max_fragmented_header_block_size has been added to limit the size of header blocks that are sent over multiple HEADERS and CONTINUATION frames.  Update Cowlib to 2.13.0.   Bugs fixed Gun will no longer configure the NPN TLS extension, which has long been replaced by ALPN.</description>
+    </item>
+    
+    <item>
       <title>Constraints</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/guide/constraints/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1372,6 +1544,18 @@ A field can take the form of an atom field, a tuple with constraints {field, Con
     
     <item>
       <title>Constraints</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/constraints/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/constraints/</guid>
+      <description>Constraints are validation and conversion functions applied to user input.
+They are used in various places in Cowboy, including the router and the cowboy_req match functions.
+Syntax Constraints are provided as a list of fields. For each field in the list, specific constraints can be applied, as well as a default value if the field is missing.
+A field can take the form of an atom field, a tuple with constraints {field, Constraints} or a tuple with constraints and a default value {field, Constraints, Default}.</description>
+    </item>
+    
+    <item>
+      <title>Constraints</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/constraints/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -1506,6 +1690,19 @@ init(Req, State) -&amp;gt; {ok, Req, State}.  Despite sending no reply, a 204 No
     
     <item>
       <title>Handlers</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/handlers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/handlers/</guid>
+      <description>Handlers are Erlang modules that handle HTTP requests.
+Plain HTTP handlers The most basic handler in Cowboy implements the mandatory init/2 callback, manipulates the request, optionally sends a response and then returns.
+This callback receives the Req object and the initial state defined in the router configuration.
+A handler that does nothing would look like this:
+init(Req, State) -&amp;gt; {ok, Req, State}.  Despite sending no reply, a 204 No Content response will be sent to the client, as Cowboy makes sure that a response is sent for every request.</description>
+    </item>
+    
+    <item>
+      <title>Handlers</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/handlers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -1567,6 +1764,16 @@ Gun 2.0 adds many more features such as Websocket over HTTP/2, a built-in cookie
     </item>
     
     <item>
+      <title>Migrating from Gun 1.3 to 2.0</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_1.3/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_1.3/</guid>
+      <description>Gun 2.0 includes state of the art tunnel support. With Gun 2.0 it is possible to make requests or data go through any number of proxy endpoints using any combination of TCP or TLS transports and HTTP/1.1, HTTP/2 or SOCKS5 protocols. All combinations of the scenario Proxy1 -&amp;gt; Proxy2 -&amp;gt; Origin are tested and known to work.
+Gun 2.0 adds many more features such as Websocket over HTTP/2, a built-in cookie store, graceful shutdown, flow control for data messages, event handlers and more.</description>
+    </item>
+    
+    <item>
       <title>Migrating from Ranch 1.7 to Ranch 2.0</title>
       <link>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1643,6 +1850,16 @@ Loop handlers are used for requests where a response might not be immediately av
     
     <item>
       <title>Loop handlers</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/loop_handlers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/loop_handlers/</guid>
+      <description>Loop handlers are a special kind of HTTP handlers used when the response can not be sent right away. The handler enters instead a receive loop waiting for the right message before it can send a response.
+Loop handlers are used for requests where a response might not be immediately available, but where you would like to keep the connection open for a while in case the response arrives. The most known example of such practice is known as long polling.</description>
+    </item>
+    
+    <item>
+      <title>Loop handlers</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/loop_handlers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -1702,6 +1919,16 @@ Features added The protocols CONNECT destination option has been added as a repl
     </item>
     
     <item>
+      <title>Migrating from Gun 1.2 to 1.3</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_1.2/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_1.2/</guid>
+      <description>Gun 1.3 improves the support for CONNECT requests introduced in the previous version and documents Websocket protocol negotiation.
+Features added The protocols CONNECT destination option has been added as a replacement for the now deprecated protocol option.  Add built-in support for Websocket protocol negotiation through the Websocket option protocols. The interface of the handler module currently remains undocumented and must be set to gun_ws_h.  Add the h2specd HTTP/2 test suite from the h2spec project.</description>
+    </item>
+    
+    <item>
       <title>Static files</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/guide/static_files/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1725,6 +1952,17 @@ The static handler can serve either one file or all files from a given directory
     
     <item>
       <title>Static files</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/static_files/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/static_files/</guid>
+      <description>Cowboy comes with a ready to use handler for serving static files. It is provided as a convenience for serving files during development.
+For systems in production, consider using one of the many Content Distribution Network (CDN) available on the market, as they are the best solution for serving files.
+The static handler can serve either one file or all files from a given directory. The etag generation and mime types can be configured.</description>
+    </item>
+    
+    <item>
+      <title>Static files</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/static_files/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -1832,6 +2070,16 @@ Features added CONNECT requests can now be issued on HTTP/1.1 connections. The t
     </item>
     
     <item>
+      <title>Migrating from Gun 1.1 to 1.2</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_1.1/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_1.1/</guid>
+      <description>Gun 1.2 adds support for the CONNECT request over HTTP/1.1 connections.
+Features added CONNECT requests can now be issued on HTTP/1.1 connections. The tunneled connection can use any of the protocols Gun supports: HTTP/1.1, HTTP/2 and Websocket over both TCP and TLS transports. Note that Gun currently does not support tunneling a TLS connection over a TLS connection due to limitations in Erlang/OTP.  Gun supports sending multiple CONNECT requests, allowing the tunnel to the origin server to go through multiple proxies.</description>
+    </item>
+    
+    <item>
       <title>The Req object</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/guide/req/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1855,6 +2103,17 @@ The Req object is the subject of a few different chapters. In this chapter we wi
     
     <item>
       <title>The Req object</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/req/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/req/</guid>
+      <description>The Req object is a variable used for obtaining information about a request, read its body or send a response.
+It is not really an object in the object-oriented sense. It is a simple map that can be directly accessed or used when calling functions from the cowboy_req module.
+The Req object is the subject of a few different chapters. In this chapter we will learn about the Req object and look at how to retrieve information about the request.</description>
+    </item>
+    
+    <item>
+      <title>The Req object</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/req/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -1977,6 +2236,18 @@ You are not required to read it, however. If a body is present and was not read,
     
     <item>
       <title>Reading the request body</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/req_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/req_body/</guid>
+      <description>The request body can be read using the Req object.
+Cowboy will not attempt to read the body until requested. You need to call the body reading functions in order to retrieve it.
+Cowboy will not cache the body, it is therefore only possible to read it once.
+You are not required to read it, however. If a body is present and was not read, Cowboy will either cancel or skip its download, depending on the protocol.</description>
+    </item>
+    
+    <item>
+      <title>Reading the request body</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/req_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2034,6 +2305,16 @@ Features added Update Cowlib to 2.5.1   Bugs fixed A bug in the experimental gun
     </item>
     
     <item>
+      <title>Migrating from Gun 1.0 to 1.1</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_1.0/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/migrating_from_1.0/</guid>
+      <description>Gun 1.1 updates the Cowlib dependency to 2.5.1 and fixes a few problems with experimental features.
+Features added Update Cowlib to 2.5.1   Bugs fixed A bug in the experimental gun_sse_h where lone id lines were not propagated has been fixed by updating the Cowlib dependency.  The status code was incorrectly given to the experimental content handlers as a binary. It has been fixed an an integer is now given as was intended.</description>
+    </item>
+    
+    <item>
       <title>Sending a response</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/guide/resp/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2059,6 +2340,18 @@ While only one response is allowed for every request, HTTP/2 introduced a mechan
     
     <item>
       <title>Sending a response</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/resp/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/resp/</guid>
+      <description>The response must be sent using the Req object.
+Cowboy provides two different ways of sending responses: either directly or by streaming the body. Response headers and body may be set in advance. The response is sent as soon as one of the reply or stream reply function is called.
+Cowboy also provides a simplified interface for sending files. It can also send only specific parts of a file.
+While only one response is allowed for every request, HTTP/2 introduced a mechanism that allows the server to push additional resources related to the response.</description>
+    </item>
+    
+    <item>
+      <title>Sending a response</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/resp/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2168,6 +2461,16 @@ Cookies are a name/value store where the names and values are stored in plain te
     
     <item>
       <title>Using cookies</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/cookies/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/cookies/</guid>
+      <description>Cookies are a mechanism allowing applications to maintain state on top of the stateless HTTP protocol.
+Cookies are a name/value store where the names and values are stored in plain text. They expire either after a delay or when the browser closes. They can be configured on a specific domain name or path, and restricted to secure resources (sent or downloaded over HTTPS), or restricted to the server (disallowing access from client-side scripts).</description>
+    </item>
+    
+    <item>
+      <title>Using cookies</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/cookies/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2230,6 +2533,17 @@ In the context of HTTP, multipart is most often used with the multipart/form-dat
     
     <item>
       <title>Multipart requests</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/multipart/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/multipart/</guid>
+      <description>Multipart originates from MIME, an Internet standard that extends the format of emails.
+A multipart message is a list of parts. A part contains headers and a body. The body of the parts may be of any media type, and contain text or binary data. It is possible for parts to contain a multipart media type.
+In the context of HTTP, multipart is most often used with the multipart/form-data media type.</description>
+    </item>
+    
+    <item>
+      <title>Multipart requests</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/multipart/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2306,6 +2620,17 @@ We will first attempt to define REST and will look at what it means in the conte
     
     <item>
       <title>REST principles</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/rest_principles/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/rest_principles/</guid>
+      <description>This chapter will attempt to define the concepts behind REST and explain what makes a service RESTful.
+REST is often confused with performing a distinct operation depending on the HTTP method, while using more than the GET and POST methods. That&amp;apos;s highly misguided at best.
+We will first attempt to define REST and will look at what it means in the context of HTTP and the Web. For a more in-depth explanation of REST, you can read Roy T.</description>
+    </item>
+    
+    <item>
+      <title>REST principles</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_principles/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2374,6 +2699,18 @@ init(Req, State) -&amp;gt; {cowboy_rest, Req, State}.</description>
     
     <item>
       <title>REST handlers</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/rest_handlers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/rest_handlers/</guid>
+      <description>REST is implemented in Cowboy as a sub protocol. The request is handled as a state machine with many optional callbacks describing the resource and modifying the machine&amp;apos;s behavior.
+The REST handler is the recommended way to handle HTTP requests.
+Initialization First, the init/2 callback is called. This callback is common to all handlers. To use REST for the current request, this function must return a cowboy_rest tuple.
+init(Req, State) -&amp;gt; {cowboy_rest, Req, State}.</description>
+    </item>
+    
+    <item>
+      <title>REST handlers</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_handlers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2444,6 +2781,17 @@ All paths start with the &amp;quot;Start&amp;quot; diagram, and all paths exclud
     
     <item>
       <title>REST flowcharts</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/rest_flowcharts/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/rest_flowcharts/</guid>
+      <description>This chapter will explain the REST handler state machine through a number of different diagrams.
+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.
+All paths start with the &amp;quot;Start&amp;quot; diagram, and all paths excluding the OPTIONS path go through the &amp;quot;Content negotiation&amp;quot; diagram and optionally the &amp;quot;Conditional requests&amp;quot; diagram if the resource exists.</description>
+    </item>
+    
+    <item>
+      <title>REST flowcharts</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_flowcharts/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2508,6 +2856,16 @@ The service Can the service become unavailable, and when it does, can we detect
     
     <item>
       <title>Designing a resource handler</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/resource_design/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/resource_design/</guid>
+      <description>This chapter aims to provide you with a list of questions you must answer in order to write a good resource handler. It is meant to be usable as a step by step guide.
+The service Can the service become unavailable, and when it does, can we detect it? For example, database connectivity problems may be detected early. We may also have planned outages of all or parts of the system.</description>
+    </item>
+    
+    <item>
+      <title>Designing a resource handler</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/resource_design/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2570,6 +2928,17 @@ Websocket connections are fully asynchronous, unlike HTTP/1.1 (synchronous) and
     
     <item>
       <title>The Websocket protocol</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/ws_protocol/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/ws_protocol/</guid>
+      <description>This chapter explains what Websocket is and why it is a vital component of soft realtime Web applications.
+Description Websocket is an extension to HTTP that emulates plain TCP connections between the client, typically a Web browser, and the server. It uses the HTTP Upgrade mechanism to establish the connection.
+Websocket connections are fully asynchronous, unlike HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the server can only initiate streams in response to requests).</description>
+    </item>
+    
+    <item>
+      <title>The Websocket protocol</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/ws_protocol/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2634,6 +3003,16 @@ As Websocket connections are established through the HTTP/1.1 upgrade mechanism,
     
     <item>
       <title>Websocket handlers</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/ws_handlers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/ws_handlers/</guid>
+      <description>Websocket handlers provide an interface for upgrading HTTP/1.1 connections to Websocket and sending or receiving frames on the Websocket connection.
+As Websocket connections are established through the HTTP/1.1 upgrade mechanism, Websocket handlers need to be able to first receive the HTTP request for the upgrade, before switching to Websocket and taking over the connection. They can then receive or send Websocket frames, handle incoming Erlang messages or close the connection.</description>
+    </item>
+    
+    <item>
+      <title>Websocket handlers</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/ws_handlers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2696,6 +3075,17 @@ All versions of HTTP allow clients to initiate streams. HTTP/2 is the only one a
     
     <item>
       <title>Streams</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/streams/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/streams/</guid>
+      <description>A stream is the set of messages that form an HTTP request/response pair.
+The term stream comes from HTTP/2. In Cowboy, it is also used when talking about HTTP/1.1 or HTTP/1.0. It should not be confused with streaming the request or response body.
+All versions of HTTP allow clients to initiate streams. HTTP/2 is the only one also allowing servers, through its server push feature. Both client and server-initiated streams go through the same process in Cowboy.</description>
+    </item>
+    
+    <item>
+      <title>Streams</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/streams/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2762,6 +3152,17 @@ Cowboy will execute all middlewares in the given order, unless one of them decid
     
     <item>
       <title>Middlewares</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/middlewares/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/middlewares/</guid>
+      <description>Cowboy delegates the request processing to middleware components. By default, two middlewares are defined, for the routing and handling of the request, as is detailed in most of this guide.
+Middlewares give you complete control over how requests are to be processed. You can add your own middlewares to the mix or completely change the chain of middlewares as needed.
+Cowboy will execute all middlewares in the given order, unless one of them decides to stop processing.</description>
+    </item>
+    
+    <item>
+      <title>Middlewares</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/middlewares/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2848,6 +3249,16 @@ One process per connection The first version of Cowboy featured a single process
     
     <item>
       <title>Performance</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/performance/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/performance/</guid>
+      <description>This chapter describes the performance characteristics of Cowboy and offers suggestions to get the most performance out of your application.
+One process per connection The first version of Cowboy featured a single process per connection, whereas the current version of Cowboy features one process per connection plus one process per request. This has a negative impact on performance, but is necessary in order to provide a common interface for both HTTP/1.</description>
+    </item>
+    
+    <item>
+      <title>Performance</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.8/guide/performance/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -2878,6 +3289,17 @@ Cowboy is now using GitHub Actions for CI. The main reason for the move is to re
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.11 to 2.12</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.11/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.11/</guid>
+      <description>Cowboy 2.12 contains a small security improvement for the HTTP/2 protocol.
+Cowboy 2.12 requires Erlang/OTP 24.0 or greater.
+Features added A new HTTP/2 option max_fragmented_header_block_size has been added to limit the size of header blocks that are sent over multiple HEADERS and CONTINUATION frames.  Update Cowlib to 2.13.0.   </description>
+    </item>
+    
+    <item>
       <title>Migrating from Cowboy 2.7 to 2.8</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.8/guide/migrating_from_2.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2962,6 +3384,17 @@ Cowboy 2.9 also contains a small number of tweaks and bug fixes.</description>
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.10 to 2.11</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.10/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.10/</guid>
+      <description>Cowboy 2.11 contains a variety of new features and bug fixes. Nearly all previously experimental features are now marked as stable, including Websocket over HTTP/2. Included is a fix for an HTTP/2 protocol CVE.
+Cowboy 2.11 requires Erlang/OTP 24.0 or greater.
+Cowboy is now using GitHub Actions for CI. The main reason for the move is to reduce costs by no longer having to self-host CI runners. The downside is that GitHub runners are less reliable and timing dependent tests are now more likely to fail.</description>
+    </item>
+    
+    <item>
       <title>Migrating from Cowboy 2.9 to 2.10</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.11/guide/migrating_from_2.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3034,6 +3467,17 @@ Cowboy 2.9 also contains a small number of tweaks and bug fixes.</description>
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.9 to 2.10</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.9/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.9/</guid>
+      <description>Cowboy 2.10 is a maintenance release adding support for Erlang/OTP 26. The main change is a Cowlib update to fix a compilation error that only occurs starting from OTP 26.
+Cowboy 2.10 requires Erlang/OTP 22.0 or greater.
+Features added Add support for Default value of SameSite cookie attribute.  Add support for the stale-* cache-control directives from RFC 5861.  Update Cowlib to 2.12.1.   Bugs fixed Fix a compilation error in Cowlib when using Erlang/OTP 26.</description>
+    </item>
+    
+    <item>
       <title>Migrating from Cowboy 2.3 to 2.4</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3094,6 +3538,17 @@ Cowboy 2.8 also contains a small number of tweaks and bug fixes. Cowboy 2.8 is t
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.8 to 2.9</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.8/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.8/</guid>
+      <description>Cowboy 2.9 implements graceful shutdown of connection processes for both HTTP/1.1 and HTTP/2 connections.
+Cowboy 2.9 is the first release to support the much awaited Erlang/OTP 24 out of the box. While users that were using Ranch 2.0 already were ready for OTP 24, the Ranch version used by Cowboy out of the box was not compatible and had to be updated.
+Cowboy 2.9 also contains a small number of tweaks and bug fixes.</description>
+    </item>
+    
+    <item>
       <title>Migrating from Cowboy 2.2 to 2.3</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3154,6 +3609,16 @@ Features added Add support for the PROXY protocol header. It can be enabled via
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.7 to 2.8</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.7/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.7/</guid>
+      <description>Cowboy 2.8 contains many optimizations for all protocols. HTTP/1.1 has received the largest improvements and Cowboy will now be able to handle noticeably more requests. Thanks to the folks at Stressgrid for helping identify that the performance was lower than it should have been and for benchmarking my many changes and experiments.
+Cowboy 2.8 also contains a small number of tweaks and bug fixes. Cowboy 2.8 is the first Cowboy release, ever, to be consistently green on all tested platforms.</description>
+    </item>
+    
+    <item>
       <title>Migrating from Cowboy 2.1 to 2.2</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3215,6 +3680,15 @@ Features added Add support for the PROXY protocol header. It can be enabled via
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.6 to 2.7</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.6/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.6/</guid>
+      <description>Cowboy 2.7 improves the HTTP/2 code with optimizations around the sending of DATA and WINDOW_UPDATE frames; graceful shutdown of the connection when the client is going away; and rate limiting mechanisms. New options and mechanisms have also been added to control the amount of memory Cowboy ends up using with both HTTP/1.1 and HTTP/2. Much, but not all, of this work was done to address HTTP/2 CVEs about potential denial of service.</description>
+    </item>
+    
+    <item>
       <title>Migrating from Cowboy 2.0 to 2.1</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3275,6 +3749,17 @@ Features added Add option linger_timeout to control how long Cowboy will wait be
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.5 to 2.6</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.5/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.5/</guid>
+      <description>Cowboy 2.6 greatly refactored the HTTP/2 code, a large part of which was moved to Cowlib and is now used by both the Cowboy server and the Gun client.
+A large number of tickets were also closed which resulted in many bugs fixed and many features and options added, although some of them are still experimental.
+Features added Add support for the PROXY protocol header. It can be enabled via the proxy_header option.</description>
+    </item>
+    
+    <item>
       <title>Migrating from Cowboy 1.0 to 2.0</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3337,6 +3822,16 @@ Features added Add experimental support for Websocket over HTTP/2. You can use t
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.4 to 2.5</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.4/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.4/</guid>
+      <description>Cowboy 2.5 focused on making the test suites pass. A variety of new features, fixes and improvements have also been worked on.
+Features added Add option linger_timeout to control how long Cowboy will wait before closing the socket when shutting down the connection. This helps avoid the TCP reset problem HTTP/1.1 suffers from. The default is now 1000 ms.  It is now possible to stream a response body without using chunked transfer-encoding when the protocol is HTTP/1.</description>
+    </item>
+    
+    <item>
       <title>HTTP and other specifications</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/specs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3398,6 +3893,16 @@ Features added Add support for all functions from the module sys. Note that Cowb
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.3 to 2.4</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.3/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.3/</guid>
+      <description>Cowboy 2.4 focused on improving the HTTP/2 implementation. All existing tests from RFC7540 and the h2spec test suite now all pass. Numerous options have been added to control SETTINGS and related behavior. In addition experimental support for Websocket over HTTP/2 was added.
+Features added Add experimental support for Websocket over HTTP/2. You can use the enable_connect_protocol option to enable. It implements the following draft: https://tools.ietf.org/html/draft-ietf-httpbis-h2-websockets-01  Add options max_decode_table_size and max_encode_table_size to restrict the size of the HPACK compression dictionary.</description>
+    </item>
+    
+    <item>
       <title>HTTP and other specifications</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.8/guide/specs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3439,6 +3944,16 @@ Features added Add support for sending trailers at the end of response bodies. T
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.2 to 2.3</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.2/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.2/</guid>
+      <description>Cowboy 2.3 focused on making the Cowboy processes behave properly according to OTP principles. This version is a very good milestone toward that goal and most of everything should now work. Release upgrades and a few details will be improved in future versions.
+Features added Add support for all functions from the module sys. Note that Cowboy currently does not implement the sys debugging mechanisms as tracing is recommended instead.  Add a max_frame_size option for Websocket handlers to close the connection when the client attempts to send a frame that&amp;apos;s too large.</description>
+    </item>
+    
+    <item>
       <title>HTTP and other specifications</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.9/guide/specs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3470,6 +3985,16 @@ Features added It is now possible to obtain the client TLS certificate and the l
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.1 to 2.2</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.1/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.1/</guid>
+      <description>Cowboy 2.2 focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs, fixing many bugs along the way.
+Features added Add support for sending trailers at the end of response bodies. Trailers are additional header fields that may be sent after the body to add more information to the response. Their usage is required in gRPC servers. They are optional and may be discarded in other scenarios (for example if the request goes through an HTTP/1.</description>
+    </item>
+    
+    <item>
       <title>HTTP and other specifications</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/guide/specs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3491,6 +4016,16 @@ Compatibility Compatibility with Erlang/OTP R16, 17 and 18 has been dropped. Erl
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.0 to 2.1</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.0/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_2.0/</guid>
+      <description>Cowboy 2.1 focused on adding features that were temporarily removed in Cowboy 2.0. A number of bugs found in the 2.0 release were also fixed.
+Features added It is now possible to obtain the client TLS certificate and the local IP/port for the connection from the Req object.  Informational responses (1XX responses) can now be sent. They must be sent before initiating the final response.  The expect: 100-continue header is now handled automatically.</description>
+    </item>
+    
+    <item>
       <title>HTTP and other specifications</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.11/guide/specs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3501,6 +4036,27 @@ HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message He
     </item>
     
     <item>
+      <title>Migrating from Cowboy 1.0 to 2.0</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_1.0/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/migrating_from_1.0/</guid>
+      <description>A lot has changed between Cowboy 1.0 and 2.0. The cowboy_req interface in particular has seen a massive revamp. Hooks are gone, their functionality can now be achieved via stream handlers.
+The documentation has seen great work, in particular the manual. Each module and each function now has its own dedicated manual page with full details and examples.
+Compatibility Compatibility with Erlang/OTP R16, 17 and 18 has been dropped. Erlang/OTP 19.</description>
+    </item>
+    
+    <item>
+      <title>HTTP and other specifications</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/specs/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/specs/</guid>
+      <description>This chapter intends to list all the specification documents for or related to HTTP.
+HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message Headers  HTTP Parameters  HTTP Alt-Svc Parameter Registry  HTTP Authentication Scheme Registry  HTTP Cache Directive Registry  HTTP Digest Algorithm Values  HTTP Origin-Bound Authentication Device Identifier Types  HTTP Upgrade Token Registry  HTTP Warn Codes  HTTP/2 Parameters  WebSocket Protocol Registries   Current CORS: Cross-Origin Resource Sharing  CSP2: Content Security Policy Level 2  DNT: Tracking Preference Expression (DNT)  eventsource: Server-Sent Events  Form content types: Form content types  Preload: Preload  PROXY: The PROXY protocol  REST: Fielding&amp;apos;s Dissertation  RFC 1945: HTTP/1.</description>
+    </item>
+    
+    <item>
       <title>Cowboy 2.11</title>
       <link>https://ninenines.eu/articles/cowboy-2.11.0/</link>
       <pubDate>Mon, 29 Jan 2024 07:00:00 +0100</pubDate>
@@ -4239,6 +4795,17 @@ Exports cow_cookie:parse_cookie(3) - Parse a cookie header  cow_cookie:parse_set
     
     <item>
       <title>cow_cookie(3)</title>
+      <link>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie/</guid>
+      <description>Name cow_cookie - Cookies
+Description The module cow_cookie provides functions for parsing and manipulating cookie headers.
+Exports cow_cookie:parse_cookie(3) - Parse a cookie header  cow_cookie:parse_set_cookie(3) - Parse a set-cookie header  cow_cookie:cookie(3) - Generate a cookie header  cow_cookie:setcookie(3) - Generate a set-cookie header   Types cookie_attrs() cookie_attrs() :: #{ expires =&amp;gt; calendar:datetime(), max_age =&amp;gt; calendar:datetime(), domain =&amp;gt; binary(), path =&amp;gt; binary(), secure =&amp;gt; true, http_only =&amp;gt; true, same_site =&amp;gt; default | none | strict | lax }  Cookie attributes parsed from the set-cookie header.</description>
+    </item>
+    
+    <item>
+      <title>cow_cookie(3)</title>
       <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4300,6 +4867,19 @@ Changelog 2.9: Function introduced.   Examples Generate a cookie header Cookie =
     
     <item>
       <title>cow_cookie:cookie(3)</title>
+      <link>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie.cookie/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie.cookie/</guid>
+      <description>Name cow_cookie:cookie - Generate a cookie header
+Description cookie(Cookies) -&amp;gt; iolist() Cookies :: [{Name :: iodata(), Value :: iodata()}]  Generate a cookie header.
+Arguments Cookies A list of pairs of cookie name and value.
+  Return value An iolist with the generated cookie header value.
+Changelog 2.9: Function introduced.   Examples Generate a cookie header Cookie = cow_cookie:cookie([{&amp;lt;&amp;lt;&#34;sessionid&#34;&amp;gt;&amp;gt;, ID}]).  See also cow_cookie(3), cow_cookie:parse_cookie(3), cow_cookie:parse_set_cookie(3), cow_cookie:setcookie(3)</description>
+    </item>
+    
+    <item>
+      <title>cow_cookie:cookie(3)</title>
       <link>https://ninenines.eu/docs/en/cowlib/2.9/manual/cow_cookie.cookie/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4355,6 +4935,20 @@ Changelog 2.9: Fixes to the parser may lead to potential incompatibilities. A co
     
     <item>
       <title>cow_cookie:parse_cookie(3)</title>
+      <link>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie.parse_cookie/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie.parse_cookie/</guid>
+      <description>Name cow_cookie:parse_cookie - Parse a cookie header
+Description parse_cookie(Cookie :: binary()) -&amp;gt; [{binary(), binary()}]  Parse a cookie header.
+Arguments Cookie The cookie header value.
+  Return value A list of cookie name/value pairs is returned on success.
+An exception is thrown in the event of a parse error.
+Changelog 2.9: Fixes to the parser may lead to potential incompatibilities. A cookie name starting with $ is no longer ignored.</description>
+    </item>
+    
+    <item>
+      <title>cow_cookie:parse_cookie(3)</title>
       <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie.parse_cookie/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4422,6 +5016,19 @@ An atom ignore is returned when the cookie has both an empty name and an empty v
     
     <item>
       <title>cow_cookie:parse_set_cookie(3)</title>
+      <link>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie.parse_set_cookie/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie.parse_set_cookie/</guid>
+      <description>Name cow_cookie:parse_set_cookie - Parse a set-cookie header
+Description parse_set_cookie(SetCookie :: binary()) -&amp;gt; {ok, Name, Value, Attrs} | ignore Name :: binary() Value :: binary() Attrs :: cow_cookie:cookie_attrs()  Parse a set-cookie header.
+Arguments SetCookie The set-cookie header value.
+  Return value An ok tuple with the cookie name, value and attributes is returned on success.
+An atom ignore is returned when the cookie has both an empty name and an empty value, and must be ignored.</description>
+    </item>
+    
+    <item>
+      <title>cow_cookie:parse_set_cookie(3)</title>
       <link>https://ninenines.eu/docs/en/cowlib/2.9/manual/cow_cookie.parse_set_cookie/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4480,6 +5087,21 @@ Changelog 2.12: The Version attribute is no longer generated.  1.0: Function int
     
     <item>
       <title>cow_cookie:setcookie(3)</title>
+      <link>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie.setcookie/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowlib/2.13/manual/cow_cookie.setcookie/</guid>
+      <description>Name cow_cookie:setcookie - Generate a set-cookie header
+Description setcookie(Name :: iodata(), Value :: iodata(), Opts :: cow_cookie:cookie_opts()) -&amp;gt; iolist()  Generate a set-cookie header.
+Arguments Name Cookie name.
+ Value Cookie value.
+ Opts Options added to the set-cookie header as attributes.
+  Return value An iolist with the generated set-cookie header value.
+Changelog 2.12: The Version attribute is no longer generated.  1.0: Function introduced.   Examples Generate a set-cookie header SetCookie = cow_cookie:setcookie(&amp;lt;&amp;lt;&#34;</description>
+    </item>
+    
+    <item>
+      <title>cow_cookie:setcookie(3)</title>
       <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie.setcookie/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4536,6 +5158,19 @@ cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_ro
     
     <item>
       <title>Cowboy Function Reference</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/</guid>
+      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
+Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
+Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
+Modules Functions:
+cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
+    </item>
+    
+    <item>
+      <title>Cowboy Function Reference</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4606,6 +5241,15 @@ cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_ro
     
     <item>
       <title>Cowboy User Guide</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/guide/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/guide/</guid>
+      <description>Rationale The modern Web  Erlang and the Web   Introduction Introduction  Getting started  Flow diagram   Configuration Listeners  Routing  Constraints   Handlers Handlers  Loop handlers  Static files   Request and response Request details  Reading the request body  Sending a response  Using cookies  Multipart   REST REST principles  Handling REST requests  REST flowcharts  Designing a resource handler   Websocket The Websocket protocol  Websocket handlers   Advanced Streams  Middlewares  Performance   Additional information Migrating from Cowboy 2.</description>
+    </item>
+    
+    <item>
+      <title>Cowboy User Guide</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4664,6 +5308,17 @@ Exports cowboy:start_clear(3) - Listen for connections using plain TCP  cowboy:s
     
     <item>
       <title>cowboy(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy/</guid>
+      <description>Name cowboy - HTTP server
+Description The module cowboy provides convenience functions for manipulating Ranch listeners.
+Exports cowboy:start_clear(3) - Listen for connections using plain TCP  cowboy:start_tls(3) - Listen for connections using TLS  cowboy:stop_listener(3) - Stop the given listener  cowboy:get_env(3) - Retrieve a listener&amp;apos;s environment value  cowboy:set_env(3) - Update a listener&amp;apos;s environment value   Types fields() fields() :: [Name | {Name, Constraints} | {Name, Constraints, Default}] Name :: atom() Constraints :: Constraint | [Constraint] Constraint :: cowboy_constraints:constraint() Default :: any()  Fields description for match operations.</description>
+    </item>
+    
+    <item>
+      <title>cowboy(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4734,6 +5389,19 @@ cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_ro
     
     <item>
       <title>cowboy(7)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_app/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_app/</guid>
+      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
+Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
+Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
+Modules Functions:
+cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
+    </item>
+    
+    <item>
+      <title>cowboy(7)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_app/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4798,6 +5466,19 @@ The name of the listener is the first argument given to the cowboy:start_clear(3
     </item>
     
     <item>
+      <title>cowboy:get_env(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.get_env/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.get_env/</guid>
+      <description>Name cowboy:get_env - Retrieve a listener&amp;apos;s environment value
+Description get_env(Name :: ranch:ref(), Key :: atom()) -&amp;gt; any() get_env(Name :: ranch:ref(), Key :: atom(), Default :: any()) -&amp;gt; any()  Retrieve an environment value for a previously started listener.
+This function may crash when the key is missing from the environment and a default value is not provided.
+Arguments Name The name of the listener to access.
+The name of the listener is the first argument given to the cowboy:start_clear(3), cowboy:start_tls(3) or ranch:start_listener(3) function.</description>
+    </item>
+    
+    <item>
       <title>cowboy:set_env(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/manual/cowboy.set_env/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4825,6 +5506,19 @@ Arguments Name The name of the listener to update.</description>
     
     <item>
       <title>cowboy:set_env(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.set_env/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.set_env/</guid>
+      <description>Name cowboy:set_env - Update a listener&amp;apos;s environment value
+Description set_env(Name :: ranch:ref(), Key :: atom(), Value :: any()) -&amp;gt; ok  Set or update an environment value for a previously started listener.
+This is most useful for updating the routes dynamically, without having to restart the listener.
+The new value will only be available to new connections. Pre-existing connections will still use the old value.
+Arguments Name The name of the listener to update.</description>
+    </item>
+    
+    <item>
+      <title>cowboy:set_env(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.set_env/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4901,6 +5595,18 @@ Arguments Name The listener name is used to refer to this listener in future cal
     
     <item>
       <title>cowboy:start_clear(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.start_clear/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.start_clear/</guid>
+      <description>Name cowboy:start_clear - Listen for connections using plain TCP
+Description start_clear(Name :: ranch:ref(), TransportOpts :: ranch_tcp:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a clear TCP channel.
+Both HTTP/1.1 and HTTP/2 are supported on this listener. HTTP/2 has two methods of establishing a connection over a clear TCP channel. Both the upgrade and the prior knowledge methods are supported.
+Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
+    </item>
+    
+    <item>
+      <title>cowboy:start_clear(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.start_clear/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -4973,6 +5679,18 @@ Arguments Name The listener name is used to refer to this listener in future cal
     
     <item>
       <title>cowboy:start_tls(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.start_tls/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.start_tls/</guid>
+      <description>Name cowboy:start_tls - Listen for connections using TLS
+Description start_tls(Name :: ranch:ref(), TransportOpts :: ranch_ssl:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a secure TLS channel.
+Both HTTP/1.1 and HTTP/2 are supported on this listener. The ALPN TLS extension must be used to initiate an HTTP/2 connection.
+Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
+    </item>
+    
+    <item>
+      <title>cowboy:start_tls(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.start_tls/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5051,6 +5769,21 @@ The {error, not_found} tuple is returned when the listener does not exist.</desc
     
     <item>
       <title>cowboy:stop_listener(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.stop_listener/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy.stop_listener/</guid>
+      <description>Name cowboy:stop_listener - Stop the given listener
+Description stop_listener(Name :: ranch:ref()) -&amp;gt; ok | {error, not_found}.  Stop a previously started listener.
+Alias of ranch:stop_listener(3).
+Arguments Name The name of the listener to be stopped.
+The name of the listener is the first argument given to the cowboy:start_clear(3), cowboy:start_tls(3) or ranch:start_listener(3) function.
+  Return value The atom ok is returned on success.
+The {error, not_found} tuple is returned when the listener does not exist.</description>
+    </item>
+    
+    <item>
+      <title>cowboy:stop_listener(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.stop_listener/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5133,6 +5866,17 @@ Normal responses will only be compressed when their size is lower than the confi
     
     <item>
       <title>cowboy_compress_h(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_compress_h/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_compress_h/</guid>
+      <description>Name cowboy_compress_h - Compress stream handler
+Description The module cowboy_compress_h compresses response bodies automatically when the client supports it. It will not try to compress responses that already have a content encoding or that have an etag header defined.
+Normal responses will only be compressed when their size is lower than the configured threshold. Streamed responses are always compressed, including when the sendfile command is used. Because the file must be read in memory to be compressed, this module is not suitable for automatically compressing large files.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_compress_h(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_compress_h/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5203,6 +5947,19 @@ cowboy_constraints:int(3) - Integer constraint  cowboy_constraints:nonempty(3) -
     
     <item>
       <title>cowboy_constraints(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_constraints/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_constraints/</guid>
+      <description>Name cowboy_constraints - Constraints
+Description The module cowboy_constraints defines the built-in constraints in Cowboy and provides an interface for manipulating these constraints.
+Constraints are functions that define what type of input is allowed. They are used throughout Cowboy, from the router to query strings to cookies.
+Exports Built-in constraints:
+cowboy_constraints:int(3) - Integer constraint  cowboy_constraints:nonempty(3) - Non-empty constraint   Types constraint() constraint() :: int | nonempty | fun()  A constraint function.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_constraints(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5281,6 +6038,19 @@ int(format_error, Error) -&amp;gt; HumanReadable Error :: {not_an_integer, Bin |
     
     <item>
       <title>cowboy_constraints:int(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_constraints.int/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_constraints.int/</guid>
+      <description>Name cowboy_constraints:int - Integer constraint
+Description Constraint functions implement a number of different operations.
+int(forward, Bin) -&amp;gt; {ok, Int} | {error, not_an_integer} Bin :: binary() Int :: integer()  Validate and convert the text representation of an integer.
+int(reverse, Int) -&amp;gt; {ok, Bin} | {error, not_an_integer}  Convert an integer back to its text representation.
+int(format_error, Error) -&amp;gt; HumanReadable Error :: {not_an_integer, Bin | Int} HumanReadable :: iolist()  Generate a human-readable error message.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_constraints:int(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints.int/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5361,6 +6131,20 @@ Arguments Arguments vary depending on the operation. Constraint functions always
     
     <item>
       <title>cowboy_constraints:nonempty(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_constraints.nonempty/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_constraints.nonempty/</guid>
+      <description>Name cowboy_constraints:nonempty - Non-empty constraint
+Description Constraint functions implement a number of different operations.
+nonempty(forward | reverse, &amp;lt;&amp;lt;&amp;gt;&amp;gt;) -&amp;gt; {error, empty}  Reject empty values.
+nonempty(forward | reverse, Bin) -&amp;gt; {ok, Bin} Bin :: binary()  Accept any other binary values.
+nonempty(format_error, Error) -&amp;gt; HumanReadable Error :: {empty, Bin} HumanReadable :: iolist()  Generate a human-readable error message.
+Arguments Arguments vary depending on the operation. Constraint functions always take the operation type as first argument, and the value as second argument.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_constraints:nonempty(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints.nonempty/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5428,6 +6212,18 @@ This stream handler always adds a field to the Req object with the name content_
     </item>
     
     <item>
+      <title>cowboy_decompress_h(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_decompress_h/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_decompress_h/</guid>
+      <description>Name cowboy_decompress_h - Decompress stream handler
+Description The module cowboy_decompress_h decompresses request bodies automatically when the server supports it.
+The only compression algorithm currently supported is the gzip algorithm. Another limitation is that decompression is only attempted when gzip is the only content-encoding in the request.
+This stream handler always adds a field to the Req object with the name content_decoded which is treated as a list of decoded content-encoding values.</description>
+    </item>
+    
+    <item>
       <title>cowboy_handler(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/manual/cowboy_handler/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5453,6 +6249,18 @@ This module also defines a callback interface for handling HTTP requests.</descr
     
     <item>
       <title>cowboy_handler(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_handler/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_handler/</guid>
+      <description>Name cowboy_handler - Plain HTTP handlers
+Description The cowboy_handler middleware executes the handler selected by the router or any other preceding middleware.
+This middleware takes the handler module and initial state from the handler and handler_opts environment values, respectively. On completion, it adds a result value to the middleware environment, containing the return value of the terminate/3 callback (if defined) and ok otherwise.
+This module also defines a callback interface for handling HTTP requests.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_handler(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_handler/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5529,6 +6337,20 @@ It is possible to remove fields from the Req object to save memory when the hand
     
     <item>
       <title>cowboy_handler:terminate(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_handler.terminate/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_handler.terminate/</guid>
+      <description>Name cowboy_handler:terminate - Terminate the handler
+Description terminate(Reason, PartialReq, State, Handler) -&amp;gt; ok Reason :: any() PartialReq :: map() State :: any() Handler :: module()  Call the optional terminate callback if it is defined.
+Make sure to use this function at the end of the execution of modules that implement custom handler behaviors.
+Arguments Reason Reason for termination.
+ PartialReq The Req object.
+It is possible to remove fields from the Req object to save memory when the handler has no concept of requests/responses.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_handler:terminate(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_handler.terminate/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5607,6 +6429,17 @@ Options opts() :: #{ active_n =&amp;gt; pos_integer(), chunked =&amp;gt; boolean
     
     <item>
       <title>cowboy_http(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_http/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_http/</guid>
+      <description>Name cowboy_http - HTTP/1.1
+Description The module cowboy_http implements HTTP/1.1 and HTTP/1.0 as a Ranch protocol.
+Options opts() :: #{ active_n =&amp;gt; pos_integer(), chunked =&amp;gt; boolean(), connection_type =&amp;gt; worker | supervisor, http10_keepalive =&amp;gt; boolean(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), initial_stream_flow_size =&amp;gt; non_neg_integer(), linger_timeout =&amp;gt; timeout(), logger =&amp;gt; module(), max_empty_lines =&amp;gt; non_neg_integer(), max_header_name_length =&amp;gt; non_neg_integer(), max_header_value_length =&amp;gt; non_neg_integer(), max_headers =&amp;gt; non_neg_integer(), max_keepalive =&amp;gt; non_neg_integer(), max_method_length =&amp;gt; non_neg_integer(), max_request_line_length =&amp;gt; non_neg_integer(), max_skip_body_length =&amp;gt; non_neg_integer(), proxy_header =&amp;gt; boolean(), request_timeout =&amp;gt; timeout(), reset_idle_timeout_on_send =&amp;gt; boolean(), sendfile =&amp;gt; boolean(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/1.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_http(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_http/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5673,6 +6506,17 @@ Options opts() :: #{ active_n =&amp;gt; pos_integer(), connection_type =&amp;gt;
     
     <item>
       <title>cowboy_http2(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_http2/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_http2/</guid>
+      <description>Name cowboy_http2 - HTTP/2
+Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
+Options opts() :: #{ active_n =&amp;gt; pos_integer(), connection_type =&amp;gt; worker | supervisor, connection_window_margin_size =&amp;gt; 0..16#7fffffff, connection_window_update_threshold =&amp;gt; 0..16#7fffffff, enable_connect_protocol =&amp;gt; boolean(), goaway_initial_timeout =&amp;gt; timeout(), goaway_complete_timeout =&amp;gt; timeout(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), initial_connection_window_size =&amp;gt; 65535..16#7fffffff, initial_stream_window_size =&amp;gt; 0..16#7fffffff, linger_timeout =&amp;gt; timeout(), logger =&amp;gt; module(), max_concurrent_streams =&amp;gt; non_neg_integer() | infinity, max_connection_buffer_size =&amp;gt; non_neg_integer(), max_connection_window_size =&amp;gt; 0..16#7fffffff, max_decode_table_size =&amp;gt; non_neg_integer(), max_encode_table_size =&amp;gt; non_neg_integer(), max_fragmented_header_block_size =&amp;gt; 16384.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_http2(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_http2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5743,6 +6587,19 @@ Loop until receiving a specific message, then send a response and stop execution
     
     <item>
       <title>cowboy_loop(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_loop/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_loop/</guid>
+      <description>Name cowboy_loop - Loop handlers
+Description The module cowboy_loop defines a callback interface for long running HTTP connections.
+You should switch to this behavior for long polling, server-sent events and similar long-running requests.
+There are generally two usage patterns:
+Loop until receiving a specific message, then send a response and stop execution (for example long polling);  Or initiate a response in init/2 and stream the body in info/3 as necessary (for example server-sent events).</description>
+    </item>
+    
+    <item>
+      <title>cowboy_loop(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_loop/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5817,6 +6674,17 @@ Types metrics() metrics() :: #{ %% The identifier for this listener. ref := ranc
     
     <item>
       <title>cowboy_metrics_h(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_metrics_h/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_metrics_h/</guid>
+      <description>Name cowboy_metrics_h - Metrics stream handler
+Description The module cowboy_metrics_h gathers metrics and other information about a stream. It then calls the configured callback with this data.
+Types metrics() metrics() :: #{ %% The identifier for this listener. ref := ranch:ref(), %% The pid for this connection. pid := pid(), %% The streamid also indicates the total number of requests on %% this connection (StreamID div 2 + 1). streamid := cowboy_stream:streamid(), %% The terminate reason is always useful.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_metrics_h(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_metrics_h/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5876,6 +6744,19 @@ execute(Req, Env) -&amp;gt; {ok, Req, Env} | {suspend, module(), atom(), [any()]
     
     <item>
       <title>cowboy_middleware(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_middleware/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_middleware/</guid>
+      <description>Name cowboy_middleware - Middlewares
+Description The module cowboy_middleware defines a callback interface for Cowboy middlewares.
+Middlewares process the request sequentially in the order they are configured.
+Callbacks Middlewares implement the following interface:
+execute(Req, Env) -&amp;gt; {ok, Req, Env} | {suspend, module(), atom(), [any()]} | {stop, Req} Req :: cowboy_req:req() Env :: cowboy_middleware:env()  The execute/2 is the only callback that needs to be implemented. It must execute the middleware and return with instructions for Cowboy.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_middleware(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_middleware/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -5952,6 +6833,18 @@ Type Name pattern Return type access no verb, parse_*, match_* Value  question h
     
     <item>
       <title>cowboy_req(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req/</guid>
+      <description>Name cowboy_req - HTTP request and response
+Description The module cowboy_req provides functions to access, manipulate and respond to requests.
+There are four types of functions in this module. They can be differentiated by their name and their return type:
+Type Name pattern Return type access no verb, parse_*, match_* Value  question has_* boolean()  modification set_* Req  action any other verb ok | {Result, Value, Req}   Any Req returned must be used in place of the one passed as argument.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6028,6 +6921,20 @@ Arguments Name Desired binding name as an atom.
     
     <item>
       <title>cowboy_req:binding(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.binding/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.binding/</guid>
+      <description>Name cowboy_req:binding - Access a value bound from the route
+Description binding(Name, Req) -&amp;gt; binding(Name, Req, undefined) binding(Name, Req, Default) -&amp;gt; any() | Default Name :: atom() Req :: cowboy_req:req() Default :: any()  Return the value for the given binding.
+Arguments Name Desired binding name as an atom.
+ Req The Req object.
+ Default Default value returned when the binding is missing.
+  Return value By default the value is a case sensitive binary string, however constraints may change the type of this value (for example automatically converting numbers to integer).</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:binding(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.binding/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6110,6 +7017,19 @@ Changelog 2.0: Only the values are returned, they are no longer wrapped in a tup
     
     <item>
       <title>cowboy_req:bindings(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.bindings/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.bindings/</guid>
+      <description>Name cowboy_req:bindings - Access all values bound from the route
+Description bindings(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:bindings()  Return a map containing all bindings.
+Arguments Req The Req object.
+  Return value By default values are case sensitive binary strings, however constraints may change the type of this value (for example automatically converting numbers to integer).
+Changelog 2.0: Only the values are returned, they are no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:bindings(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.bindings/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6188,6 +7108,19 @@ Arguments Req The Req object.
     
     <item>
       <title>cowboy_req:body_length(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.body_length/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.body_length/</guid>
+      <description>Name cowboy_req:body_length - Body length
+Description body_length(Req :: cowboy_req:req()) -&amp;gt; undefined | non_neg_integer()  Return the length of the request body.
+The length is not always known before reading the body. In those cases Cowboy will return undefined. The body length is available after the body has been fully read.
+Arguments Req The Req object.
+  Return value The length of the request body, or undefined if it is not known.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:body_length(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.body_length/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6270,6 +7203,21 @@ Changelog 2.7: Function introduced.   Examples Read the body using auto mode rea
     
     <item>
       <title>cowboy_req:cast(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.cast/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.cast/</guid>
+      <description>Name cowboy_req:cast - Cast a stream handler event
+Description cast(Event :: any(), Req :: cowboy_req:req()) -&amp;gt; ok  Cast a stream handler event.
+The event will be passed to stream handlers through the info/3 callback.
+Arguments Event The event to be sent to stream handlers.
+ Req The Req object.
+  Return value The atom ok is always returned. It can be safely ignored.
+Changelog 2.7: Function introduced.   Examples Read the body using auto mode read_body_auto_async(Req) -&amp;gt; read_body_auto_async(Req, make_ref(), &amp;lt;&amp;lt;&amp;gt;&amp;gt;).</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:cast(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.cast/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6339,6 +7287,18 @@ Using the default configuration this function will always return undefined. You
     
     <item>
       <title>cowboy_req:cert(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.cert/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.cert/</guid>
+      <description>Name cowboy_req:cert - Client TLS certificate
+Description cert(Req :: cowboy_req:req()) -&amp;gt; binary() | undefined  Return the peer&amp;apos;s TLS certificate.
+Using the default configuration this function will always return undefined. You need to explicitly configure Cowboy to request the client certificate. To do this you need to set the verify transport option to verify_peer:
+{ok, _} = cowboy:start_tls(example, [ {port, 8443}, {certfile, &#34;path/to/cert.pem&#34;}, {verify, verify_peer} ], #{ env =&amp;gt; #{dispatch =&amp;gt; Dispatch} }).</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:cert(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.cert/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6415,6 +7375,20 @@ Arguments Name Header name as a lowercase binary string.
     
     <item>
       <title>cowboy_req:delete_resp_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.delete_resp_header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.delete_resp_header/</guid>
+      <description>Name cowboy_req:delete_resp_header - Delete a response header
+Description delete_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive  Delete the given response header.
+The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
+Arguments Name Header name as a lowercase binary string.
+ Req The Req object.
+  Return value A new Req object is returned.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:delete_resp_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.delete_resp_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6495,6 +7469,18 @@ Malformed cookies are unfortunately fairly common due to the string-based interf
     
     <item>
       <title>cowboy_req:filter_cookies(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.filter_cookies/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.filter_cookies/</guid>
+      <description>Name cowboy_req:filter_cookies - Filter cookie headers
+Description filter_cookies(Names, Req) -&amp;gt; Req Names :: [atom() | binary()]  Filter cookie headers.
+This function is meant to be used before attempting to parse or match cookies in order to remove cookies that are not relevant and are potentially malformed. Because Cowboy by default crashes on malformed cookies, this function allows processing requests that would otherwise result in a 400 error.
+Malformed cookies are unfortunately fairly common due to the string-based interface provided by browsers and this function provides a middle ground between Cowboy&amp;apos;s strict behavior and chaotic real world use cases.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:filter_cookies(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.filter_cookies/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6557,6 +7543,19 @@ Changelog 1.0: Function introduced.   Examples Ensure the request has a body tru
     
     <item>
       <title>cowboy_req:has_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.has_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.has_body/</guid>
+      <description>Name cowboy_req:has_body - Is there a request body?
+Description has_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether the request has a body.
+Arguments Req The Req object.
+  Return value A boolean indicating whether the request has a body.
+Changelog 1.0: Function introduced.   Examples Ensure the request has a body true = cowboy_req:has_body(Req).  See also cowboy_req(3), cowboy_req:body_length(3), cowboy_req:read_body(3), cowboy_req:read_urlencoded_body(3), cowboy_req:read_part(3), cowboy_req:read_part_body(3)</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:has_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6637,6 +7636,20 @@ Changelog 1.0: Function introduced.   Examples Check whether a body has been set
     
     <item>
       <title>cowboy_req:has_resp_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.has_resp_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.has_resp_body/</guid>
+      <description>Name cowboy_req:has_resp_body - Is there a response body?
+Description has_resp_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether a response body has been set.
+Arguments Req The Req object.
+  Return value A boolean indicating whether a response body has been set.
+This function will return false when an empty response body has been set.
+Changelog 1.0: Function introduced.   Examples Check whether a body has been set false = cowboy_req:has_resp_body(Req0), Req1 = cowboy_req:set_resp_body(&amp;lt;&amp;lt;&#34;</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:has_resp_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_resp_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6717,6 +7730,18 @@ Arguments Name Header name as a lowercase binary string.</description>
     
     <item>
       <title>cowboy_req:has_resp_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.has_resp_header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.has_resp_header/</guid>
+      <description>Name cowboy_req:has_resp_header - Is the given response header set?
+Description has_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; boolean() Name :: binary() %% lowercase; case insensitive  Return whether the given response header has been set.
+The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
+Arguments Name Header name as a lowercase binary string.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:has_resp_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_resp_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6789,6 +7814,18 @@ Headers can also be obtained using pattern matching:</description>
     
     <item>
       <title>cowboy_req:header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.header/</guid>
+      <description>Name cowboy_req:header - HTTP header
+Description header(Name, Req) -&amp;gt; header(Name, Req, undefined) header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given HTTP header.
+The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
+Headers can also be obtained using pattern matching:</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6865,6 +7902,20 @@ Changelog 2.0: Only the headers are returned, they are no longer wrapped in a tu
     
     <item>
       <title>cowboy_req:headers(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.headers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.headers/</guid>
+      <description>Name cowboy_req:headers - HTTP headers
+Description headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all request headers.
+Request headers can also be obtained using pattern matching:
+#{headers := Headers} = Req.  Arguments Req The Req object.
+  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
+Changelog 2.0: Only the headers are returned, they are no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:headers(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.headers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -6949,6 +8000,20 @@ Changelog 2.0: Only the host name is returned, it is no longer wrapped in a tupl
     
     <item>
       <title>cowboy_req:host(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.host/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.host/</guid>
+      <description>Name cowboy_req:host - URI host name
+Description host(Req :: cowboy_req:req()) -&amp;gt; Host :: binary()  Return the host name of the effective request URI.
+The host name can also be obtained using pattern matching:
+#{host := Host} = Req.  Arguments Req The Req object.
+  Return value The host name is returned as a lowercase binary string. It is case insensitive.
+Changelog 2.0: Only the host name is returned, it is no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:host(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.host/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7033,6 +8098,20 @@ Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tup
     
     <item>
       <title>cowboy_req:host_info(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.host_info/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.host_info/</guid>
+      <description>Name cowboy_req:host_info - Access the route&amp;apos;s heading host segments
+Description host_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the heading host segments.
+This is the part of the host name that was matched using the ... notation.
+Arguments Req The Req object.
+  Return value The tokens are returned as a list of case insensitive binary strings.
+Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:host_info(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.host_info/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7113,6 +8192,18 @@ Any number of informational responses can be sent as long as they are sent befor
     
     <item>
       <title>cowboy_req:inform(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.inform/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.inform/</guid>
+      <description>Name cowboy_req:inform - Send an informational response
+Description inform(Status, Req :: cowboy_req:req()) -&amp;gt; inform(StatusCode, #{}, Req) inform(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; ok Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send an informational response.
+Informational responses use a status code between 100 and 199. They cannot include a body. This function will not use any of the previously set headers. All headers to be sent must be given directly.
+Any number of informational responses can be sent as long as they are sent before the proper response.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:inform(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.inform/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7183,6 +8274,17 @@ Cowboy will only return the cookie values specified in the fields list, and igno
     
     <item>
       <title>cowboy_req:match_cookies(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.match_cookies/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.match_cookies/</guid>
+      <description>Name cowboy_req:match_cookies - Match cookies against constraints
+Description match_cookies(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the cookies and match specific values against constraints.
+Cowboy will only return the cookie values specified in the fields list, and ignore all others. Fields can be either the name of the cookie requested; the name along with a list of constraints; or the name, a list of constraints and a default value in case the cookie is missing.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:match_cookies(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.match_cookies/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7249,6 +8351,17 @@ Cowboy will only return the query string values specified in the fields list, an
     
     <item>
       <title>cowboy_req:match_qs(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.match_qs/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.match_qs/</guid>
+      <description>Name cowboy_req:match_qs - Match the query string against constraints
+Description match_qs(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the query string and match specific values against constraints.
+Cowboy will only return the query string values specified in the fields list, and ignore all others. Fields can be either the key requested; the key along with a list of constraints; or the key, a list of constraints and a default value in case the key is missing.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:match_qs(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.match_qs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7321,6 +8434,20 @@ Changelog 2.0: Only the method is returned, it is no longer wrapped in a tuple.<
     
     <item>
       <title>cowboy_req:method(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.method/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.method/</guid>
+      <description>Name cowboy_req:method - HTTP method
+Description method(Req :: cowboy_req:req()) -&amp;gt; Method :: binary()  Return the request&amp;apos;s HTTP method.
+The method can also be obtained using pattern matching:
+#{method := Method} = Req.  Arguments Req The Req object.
+  Return value The request&amp;apos;s HTTP method is returned as a binary string. While methods are case sensitive, standard methods are always uppercase.
+Changelog 2.0: Only the method is returned, it is no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:method(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.method/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7403,6 +8530,19 @@ This function will crash on invalid cookie data. Because invalid cookies are fai
     
     <item>
       <title>cowboy_req:parse_cookies(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.parse_cookies/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.parse_cookies/</guid>
+      <description>Name cowboy_req:parse_cookies - Parse cookie headers
+Description parse_cookies(Req) -&amp;gt; [{Name, Value}] Name :: binary() %% case sensitive Value :: binary() %% case sensitive  Parse cookie headers.
+Alias for cowboy_req:parse_header(&amp;lt;&amp;lt;&amp;quot;cookie&amp;quot;&amp;gt;&amp;gt;, Req).
+When the cookie header is missing or empty, [] is returned.
+This function will crash on invalid cookie data. Because invalid cookies are fairly common when dealing with browsers (because of the string interface that the Javascript API provides), it is recommended to filter the cookie header value before attempting to parse it.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:parse_cookies(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_cookies/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7481,6 +8621,18 @@ The type of the parsed value varies depending on the header.</description>
     
     <item>
       <title>cowboy_req:parse_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.parse_header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.parse_header/</guid>
+      <description>Name cowboy_req:parse_header - Parse the given HTTP header
+Description parse_header(Name, Req) -&amp;gt; ParsedValue | Default parse_header(Name, Req, Default) -&amp;gt; ParsedValue | Default Name :: binary() Req :: cowboy_req:req() ParsedValue :: any() Default :: any()  Parse the given HTTP header.
+The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
+The type of the parsed value varies depending on the header.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:parse_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7553,6 +8705,18 @@ Arguments Req The Req object.
     
     <item>
       <title>cowboy_req:parse_qs(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.parse_qs/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.parse_qs/</guid>
+      <description>Name cowboy_req:parse_qs - Parse the query string
+Description parse_qs(Req :: cowboy_req:req()) -&amp;gt; [{Key :: binary(), Value :: binary() | true}]  Parse the query string as a list of key/value pairs.
+Arguments Req The Req object.
+  Return value The parsed query string is returned as a list of key/value pairs. The key is a binary string. The value is either a binary string, or the atom true. Both key and value are case sensitive.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:parse_qs(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_qs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7629,6 +8793,20 @@ Changelog 2.0: Only the path is returned, it is no longer wrapped in a tuple.</d
     
     <item>
       <title>cowboy_req:path(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.path/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.path/</guid>
+      <description>Name cowboy_req:path - URI path
+Description path(Req :: cowboy_req:req()) -&amp;gt; Path :: binary()  Return the path of the effective request URI.
+The path can also be obtained using pattern matching:
+#{path := Path} = Req.  Arguments Req The Req object.
+  Return value The path is returned as a binary string. It is case sensitive.
+Changelog 2.0: Only the path is returned, it is no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:path(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.path/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7713,6 +8891,20 @@ Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tup
     
     <item>
       <title>cowboy_req:path_info(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.path_info/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.path_info/</guid>
+      <description>Name cowboy_req:path_info - Access the route&amp;apos;s trailing path segments
+Description path_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the trailing path segments.
+This is the part of the host name that was matched using the ... notation.
+Arguments Req The Req object.
+  Return value The tokens are returned as a list of case sensitive binary strings.
+Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:path_info(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.path_info/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7797,6 +8989,20 @@ The peer is not necessarily the client&amp;apos;s IP address and port. It is the
     
     <item>
       <title>cowboy_req:peer(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.peer/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.peer/</guid>
+      <description>Name cowboy_req:peer - Peer address and port
+Description peer(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the peer&amp;apos;s IP address and port number.
+The peer information can also be obtained using pattern matching:
+#{peer := {IP, Port}} = Req.  Arguments Req The Req object.
+  Return value The peer&amp;apos;s IP address and port number.
+The peer is not necessarily the client&amp;apos;s IP address and port. It is the IP address of the endpoint connecting directly to the server, which may be a gateway or a proxy.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:peer(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.peer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7879,6 +9085,19 @@ The port number can also be obtained using pattern matching:
     
     <item>
       <title>cowboy_req:port(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.port/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.port/</guid>
+      <description>Name cowboy_req:port - URI port number
+Description port(Req :: cowboy_req:req()) -&amp;gt; Port :: inet:port_number()  Return the port number of the effective request URI.
+Note that the port number returned by this function is obtained by parsing the host header. It may be different from the port the peer used to connect to Cowboy.
+The port number can also be obtained using pattern matching:
+#{port := Port} = Req.  Arguments Req The Req object.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:port(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.port/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -7953,6 +9172,17 @@ Cowboy handles push requests the same way as if they came from the client, inclu
     
     <item>
       <title>cowboy_req:push(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.push/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.push/</guid>
+      <description>Name cowboy_req:push - Push a resource to the client
+Description push(Path, Headers, Req :: cowboy_req:req()) -&amp;gt; push(Path, Headers, Req, #{}) push(Path, Headers, Req :: cowboy_req:req(), Opts) -&amp;gt; ok Path :: iodata() %% case sensitive Headers :: cowboy:http_headers() Opts :: cowboy_req:push_opts()  Push a resource to the client.
+Cowboy handles push requests the same way as if they came from the client, including the creation of a request handling process, routing and middlewares and so on.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:push(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.push/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8025,6 +9255,20 @@ Changelog 2.0: Only the query string is returned, it is no longer wrapped in a t
     
     <item>
       <title>cowboy_req:qs(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.qs/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.qs/</guid>
+      <description>Name cowboy_req:qs - URI query string
+Description qs(Req :: cowboy_req:req()) -&amp;gt; Qs :: binary()  Return the query string of the effective request URI.
+The query string can also be obtained using pattern matching:
+#{qs := Qs} = Req.  Arguments Req The Req object.
+  Return value The query string is returned as a binary string. It is case sensitive.
+Changelog 2.0: Only the query string is returned, it is no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:qs(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.qs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8103,6 +9347,17 @@ This function reads the request body and parses it as application/x-www-form-url
     
     <item>
       <title>cowboy_req:read_and_match_urlencoded_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_and_match_urlencoded_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_and_match_urlencoded_body/</guid>
+      <description>Name cowboy_req:read_and_match_urlencoded_body - Read, parse and match a urlencoded request body against constraints
+Description read_and_match_urlencoded_body(Fields, Req) -&amp;gt; read_and_match_urlencoded_body(Fields, Req, #{}) read_and_match_urlencoded_body(Fields, Req, Opts) -&amp;gt; {ok, Body, Req} Fields :: cowboy:fields() Req :: cowboy_req:req() Opts :: cowboy_req:read_body_opts() Body :: #{atom() =&amp;gt; any()}  Read, parse and match a urlencoded request body against constraints.
+This function reads the request body and parses it as application/x-www-form-urlencoded. It then applies the given field constraints to the urlencoded data and returns the result as a map.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:read_and_match_urlencoded_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_and_match_urlencoded_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8169,6 +9424,17 @@ This function reads a chunk of the request body. A more tuple is returned when m
     
     <item>
       <title>cowboy_req:read_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_body/</guid>
+      <description>Name cowboy_req:read_body - Read the request body
+Description read_body(Req :: cowboy_req:req()) -&amp;gt; read_body(Req, #{}) read_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the request body.
+This function reads a chunk of the request body. A more tuple is returned when more data remains to be read. Call the function repeatedly until an ok tuple is returned to read the entire body.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:read_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8235,6 +9501,17 @@ This function reads the request body and parses it as multipart. Each parts of a
     
     <item>
       <title>cowboy_req:read_part(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_part/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_part/</guid>
+      <description>Name cowboy_req:read_part - Read the next multipart headers
+Description read_part(Req :: cowboy_req:req()) -&amp;gt; read_part(Req, #{}) read_part(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Headers, Req} | {done, Req} Opts :: cowboy_req:read_body_opts() Headers :: #{binary() =&amp;gt; binary()}  Read the next part of a multipart body.
+This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function parses and returns headers.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:read_part(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_part/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8301,6 +9578,17 @@ This function reads the request body and parses it as multipart. Each parts of a
     
     <item>
       <title>cowboy_req:read_part_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_part_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_part_body/</guid>
+      <description>Name cowboy_req:read_part_body - Read the current part&amp;apos;s body
+Description read_part_body(Req :: cowboy_req:req()) -&amp;gt; read_part_body(Req, #{}) read_part_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the body of the current part of the multipart message.
+This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function returns the body of the current part.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:read_part_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_part_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8369,6 +9657,18 @@ The urlencoded media type is used by Web browsers when submitting HTML forms usi
     
     <item>
       <title>cowboy_req:read_urlencoded_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_urlencoded_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.read_urlencoded_body/</guid>
+      <description>Name cowboy_req:read_urlencoded_body - Read and parse a urlencoded request body
+Description read_urlencoded_body(Req :: cowboy_req:req()) -&amp;gt; read_urlencoded_body(Req, #{}) read_urlencoded_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Body, Req} Opts :: cowboy_req:read_body_opts() Body :: [{Key :: binary(), Value :: binary() | true}]  Read and parse a urlencoded request body.
+This function reads the request body and parses it as application/x-www-form-urlencoded. It returns a list of key/values.
+The urlencoded media type is used by Web browsers when submitting HTML forms using the POST method.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:read_urlencoded_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_urlencoded_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8439,6 +9739,17 @@ The header names must be given as lowercase binary strings. While header names a
     
     <item>
       <title>cowboy_req:reply(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.reply/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.reply/</guid>
+      <description>Name cowboy_req:reply - Send the response
+Description reply(Status, Req :: cowboy_req:req()) -&amp;gt; reply(StatusCode, #{}, Req) reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req reply(Status, Headers, Body, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers() Body :: cowboy_req:resp_body()  Send the response.
+The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:reply(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.reply/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8507,6 +9818,18 @@ The header name must be given as a lowercase binary string. While header names a
     
     <item>
       <title>cowboy_req:resp_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.resp_header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.resp_header/</guid>
+      <description>Name cowboy_req:resp_header - Response header
+Description resp_header(Name, Req) -&amp;gt; resp_header(Name, Req, undefined) resp_header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given response header.
+The response header must have been set previously using cowboy_req:set_resp_header(3) or cowboy_req:set_resp_headers(3).
+The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:resp_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.resp_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8581,6 +9904,19 @@ Changelog 2.0: Function introduced.   Examples Get all response headers Headers
     
     <item>
       <title>cowboy_req:resp_headers(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.resp_headers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.resp_headers/</guid>
+      <description>Name cowboy_req:resp_headers - Response headers
+Description resp_headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all response headers.
+Arguments Req The Req object.
+  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
+Changelog 2.0: Function introduced.   Examples Get all response headers Headers = cowboy_req:resp_headers(Req).  See also cowboy_req(3), cowboy_req:resp_header(3), cowboy_req:set_resp_header(3), cowboy_req:set_resp_headers(3)</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:resp_headers(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.resp_headers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8663,6 +9999,21 @@ Changelog 2.0: Function introduced.</description>
     
     <item>
       <title>cowboy_req:scheme(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.scheme/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.scheme/</guid>
+      <description>Name cowboy_req:scheme - URI scheme
+Description scheme(Req :: cowboy_req:req()) -&amp;gt; Scheme :: binary()  Return the scheme of the effective request URI.
+The scheme can also be obtained using pattern matching:
+#{scheme := Scheme} = Req.  Arguments Req The Req object.
+  Return value The scheme is returned as a binary. It is case insensitive.
+Cowboy will only set the scheme to &amp;lt;&amp;lt;&amp;quot;http&amp;quot;&amp;gt;&amp;gt; or &amp;lt;&amp;lt;&amp;quot;https&amp;quot;&amp;gt;&amp;gt;.
+Changelog 2.0: Function introduced.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:scheme(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.scheme/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8747,6 +10098,18 @@ This function can also be used to remove a response body that was set previously
     
     <item>
       <title>cowboy_req:set_resp_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.set_resp_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.set_resp_body/</guid>
+      <description>Name cowboy_req:set_resp_body - Set the response body
+Description set_resp_body(Body, Req :: cowboy_req:req()) -&amp;gt; Req Body :: cowboy_req:resp_body()  Set the response body.
+The response body will be sent when a reply is initiated. Note that the functions stream_reply/2,3 and reply/4 will override the body set by this function.
+This function can also be used to remove a response body that was set previously. To do so, simply call this function with an empty body.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:set_resp_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8823,6 +10186,20 @@ Arguments Name Cookie name.
     
     <item>
       <title>cowboy_req:set_resp_cookie(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.set_resp_cookie/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/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.
+Note that cookie names are case sensitive.
+Arguments Name Cookie name.
+ Value Cookie value.
+ Req The Req object.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:set_resp_cookie(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_cookie/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8903,6 +10280,18 @@ Cowboy does not allow duplicate header names.</description>
     
     <item>
       <title>cowboy_req:set_resp_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.set_resp_header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.set_resp_header/</guid>
+      <description>Name cowboy_req:set_resp_header - Set a response header
+Description set_resp_header(Name, Value, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive Value :: iodata() %% case depends on header  Set a header to be sent with the response.
+The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
+Cowboy does not allow duplicate header names.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:set_resp_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -8975,6 +10364,18 @@ Cowboy does not allow duplicate header names. Headers set by this function may b
     
     <item>
       <title>cowboy_req:set_resp_headers(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.set_resp_headers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.set_resp_headers/</guid>
+      <description>Name cowboy_req:set_resp_headers - Set several response headers
+Description set_resp_headers(Headers, Req :: cowboy_req:req()) -&amp;gt; Req Headers :: cowboy:http_headers()  Set several headers to be sent with the response.
+The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
+Cowboy does not allow duplicate header names. Headers set by this function may be overwritten by those set from the reply functions.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:set_resp_headers(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_headers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9051,6 +10452,20 @@ Changelog 2.1: Function introduced.   Examples Get the socket&amp;apos;s IP addr
     
     <item>
       <title>cowboy_req:sock(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.sock/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.sock/</guid>
+      <description>Name cowboy_req:sock - Socket address and port
+Description sock(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the socket&amp;apos;s IP address and port number.
+The socket information can also be obtained using pattern matching:
+#{sock := {IP, Port}} = Req.  Arguments Req The Req object.
+  Return value The socket&amp;apos;s local IP address and port number.
+Changelog 2.1: Function introduced.   Examples Get the socket&amp;apos;s IP address and port number.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:sock(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.sock/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9131,6 +10546,18 @@ The second argument indicates if this call is the final call. Use the nofin valu
     
     <item>
       <title>cowboy_req:stream_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.stream_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.stream_body/</guid>
+      <description>Name cowboy_req:stream_body - Stream the response body
+Description stream_body(Data, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Data :: cowboy_req:resp_body() IsFin :: fin | nofin  Stream the response body.
+This function may be called as many times as needed after initiating a response using the cowboy_req:stream_reply(3) function.
+The second argument indicates if this call is the final call. Use the nofin value until you know no more data will be sent. The final call should use fin (possibly with an empty data value) or be a call to the cowboy_req:stream_trailers(3) function.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:stream_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9201,6 +10628,17 @@ This function should only be used for text/event-stream responses when using ser
     
     <item>
       <title>cowboy_req:stream_events(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.stream_events/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.stream_events/</guid>
+      <description>Name cowboy_req:stream_events - Stream events
+Description stream_events(Events, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Events :: Event | [Event] IsFin :: fin | nofin Event :: #{ comment =&amp;gt; iodata(), data =&amp;gt; iodata(), event =&amp;gt; iodata() | atom(), id =&amp;gt; iodata(), retry =&amp;gt; non_neg_integer() }  Stream events.
+This function should only be used for text/event-stream responses when using server-sent events. Cowboy will automatically encode the given events to their text representation.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:stream_events(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_events/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9269,6 +10707,18 @@ Cowboy does not allow duplicate header names. Headers set by this function may o
     
     <item>
       <title>cowboy_req:stream_reply(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.stream_reply/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.stream_reply/</guid>
+      <description>Name cowboy_req:stream_reply - Send the response headers
+Description stream_reply(Status, Req :: cowboy_req:req()) -&amp;gt; stream_reply(StatusCode, #{}, Req) stream_reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send the response headers.
+The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
+Cowboy does not allow duplicate header names. Headers set by this function may overwrite those set by set_resp_header/3.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:stream_reply(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_reply/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9341,6 +10791,18 @@ You must list all field names sent in trailers in the trailer header, otherwise
     
     <item>
       <title>cowboy_req:stream_trailers(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.stream_trailers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.stream_trailers/</guid>
+      <description>Name cowboy_req:stream_trailers - Send the response trailers
+Description stream_trailers(Trailers, Req :: cowboy_req:req()) -&amp;gt; ok Trailers :: cowboy:http_headers()  Send the response trailers and terminate the stream.
+This function can only be called once, after initiating a response using cowboy_req:stream_reply(3) and sending zero or more body chunks using cowboy_req:stream_body(3) with the nofin argument set. The function stream_trailers/2 implies fin and automatically terminate the response.
+You must list all field names sent in trailers in the trailer header, otherwise they might be dropped by intermediaries or clients.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:stream_trailers(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_trailers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9411,6 +10873,17 @@ By default Cowboy will build a URI using the components found in the request.</d
     
     <item>
       <title>cowboy_req:uri(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.uri/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.uri/</guid>
+      <description>Name cowboy_req:uri - Reconstructed URI
+Description uri(Req :: cowboy_req:req()) -&amp;gt; uri(Req, #{}) uri(Req :: cowboy_req:req(), Opts) -&amp;gt; URI :: iodata() Opts :: #{ scheme =&amp;gt; iodata() | undefined, host =&amp;gt; iodata() | undefined, port =&amp;gt; inet:port_number() | undefined, path =&amp;gt; iodata() | undefined, qs =&amp;gt; iodata() | undefined, fragment =&amp;gt; iodata() | undefined }  Reconstruct the effective request URI, optionally modifying components.
+By default Cowboy will build a URI using the components found in the request.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:uri(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.uri/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9483,6 +10956,20 @@ Changelog 2.0: Only the version is returned, it is no longer wrapped in a tuple.
     
     <item>
       <title>cowboy_req:version(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.version/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_req.version/</guid>
+      <description>Name cowboy_req:version - HTTP version
+Description version(Req :: cowboy_req:req()) -&amp;gt; Version :: cowboy:http_version()  Return the HTTP version used for the request.
+The version can also be obtained using pattern matching:
+#{version := Version} = Req.  Arguments Req The Req object.
+  Return value The HTTP version used for the request is returned as an atom. It is provided for informative purposes only.
+Changelog 2.0: Only the version is returned, it is no longer wrapped in a tuple.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_req:version(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.version/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9565,6 +11052,19 @@ init(Req, State) -&amp;gt; {cowboy_rest, Req, State} Callback(Req, State) -&amp;
     
     <item>
       <title>cowboy_rest(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_rest/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_rest/</guid>
+      <description>Name cowboy_rest - REST handlers
+Description The module cowboy_rest implements the HTTP state machine.
+Implementing REST handlers is not enough to provide a REST interface; this interface must also follow the REST constraints including HATEOAS (hypermedia as the engine of application state).
+Callbacks REST handlers implement the following interface:
+init(Req, State) -&amp;gt; {cowboy_rest, Req, State} Callback(Req, State) -&amp;gt; {Result, Req, State} | {stop, Req, State} | {{switch_handler, Module}, Req, State} | {{switch_handler, Module, Opts}, Req, State} terminate(Reason, Req, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() State :: any() Module :: module() Opts :: any() Reason :: normal | {crash, error | exit | throw, any()} Callback - see below Result - see below Default - see below  The init/2 callback is common to all handlers.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_rest(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_rest/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9639,6 +11139,17 @@ The router takes the dispatch rules as input from the middleware environment. Di
     
     <item>
       <title>cowboy_router(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_router/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_router/</guid>
+      <description>Name cowboy_router - Router middleware
+Description The cowboy_router middleware maps the requested host and path to the handler to be used for processing the request.
+The router takes the dispatch rules as input from the middleware environment. Dispatch rules are generated by calling the cowboy_router:compile(3) function. The environment can contain the rules directly or a tuple {persistent_term, Key}, in which case Cowboy will call persistent_term:get(Key) to retrieve the dispatch rules.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_router(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_router/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9713,6 +11224,20 @@ Changelog 1.0: Function introduced.   Examples Compile routes and start a listen
     
     <item>
       <title>cowboy_router:compile(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_router.compile/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_router.compile/</guid>
+      <description>Name cowboy_router:compile - Compile routes to the resources
+Description compile(cowboy_router:routes()) -&amp;gt; cowboy_router:dispatch_rules()  Compile routes to the resources.
+Takes a human readable list of routes and transforms it into a form more efficient to process.
+Arguments Routes Human readable list of routes.
+  Return value An opaque dispatch rules value is returned. This value must be given to Cowboy as a middleware environment value.
+Changelog 1.0: Function introduced.   Examples Compile routes and start a listener Dispatch = cowboy_router:compile([ {&#39;_&#39;, [ {&#34;</description>
+    </item>
+    
+    <item>
+      <title>cowboy_router:compile(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_router.compile/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9793,6 +11318,18 @@ Options opts() :: {priv_file, App, Path} | {priv_file, App, Path, Extra} | {file
     
     <item>
       <title>cowboy_static(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_static/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_static/</guid>
+      <description>Name cowboy_static - Static file handler
+Description The module cowboy_static implements file serving capabilities using the REST semantics provided by cowboy_rest.
+The static file handler is a pre-written handler coming with Cowboy. To serve files, use it in your routes.
+Options opts() :: {priv_file, App, Path} | {priv_file, App, Path, Extra} | {file, Path} | {file, Path, Extra} | {priv_dir, App, Path} | {priv_dir, App, Path, Extra} | {dir, Path} | {dir, Path, Extra} App :: atom() Path :: binary() | string() Extra :: [Charset | Etag | Mimetypes] Charset :: {charset, module(), function()} | {charset, binary()} Etag :: {etag, module(), function()} | {etag, false} Mimetypes :: {mimetypes, module(), function()} | {mimetypes, binary() | ParsedMime} ParsedMime :: {Type :: binary(), SubType :: binary(), Params} Params :: [{Key :: binary(), Value :: binary()}]  Static handler configuration.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_static(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_static/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9867,6 +11404,19 @@ Extra care must be taken when implementing stream handlers to ensure compatibili
     
     <item>
       <title>cowboy_stream(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream/</guid>
+      <description>Name cowboy_stream - Stream handlers
+Description The module cowboy_stream defines a callback interface and a protocol for handling HTTP streams.
+An HTTP request and its associated response is called a stream. A connection may have many streams. In HTTP/1.1 they are executed sequentially, while in HTTP/2 they are executed concurrently.
+Cowboy calls the stream handler for nearly all events related to a stream. Exceptions vary depending on the protocol.
+Extra care must be taken when implementing stream handlers to ensure compatibility.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_stream(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_stream/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -9930,6 +11480,18 @@ Arguments StreamID The stream ID.</description>
     </item>
     
     <item>
+      <title>cowboy_stream:data(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.data/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.data/</guid>
+      <description>Name cowboy_stream:data - Handle data for a stream
+Description data(StreamID, IsFin, Data, State) -&amp;gt; {Commands, State} StreamID :: cowboy_stream:stream_id() IsFin :: cowboy_stream:fin() Data :: binary() Commands :: cowboy_stream:commands() State - opaque  Handle data for a stream.
+This function should be called by all stream handlers. It will propagate data to the next configured stream handler. Handlers do not have to propagate data that has been fully handled.
+Arguments StreamID The stream ID.</description>
+    </item>
+    
+    <item>
       <title>cowboy_stream:early_error(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.11/manual/cowboy_stream.early_error/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -9943,6 +11505,19 @@ Arguments StreamID The stream ID.
     </item>
     
     <item>
+      <title>cowboy_stream:early_error(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.early_error/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.early_error/</guid>
+      <description>Name cowboy_stream:early_error - Handle an early error for a stream
+Description early_error(StreamID, Reason, PartialReq, Resp, Opts) -&amp;gt; Resp StreamID :: cowboy_stream:stream_id() Reason :: cowboy_stream:reason() PartialReq :: cowboy_stream:partial_req() Resp :: cowboy_stream:resp_command() Opts :: cowboy:opts()  Handle an early error for a stream.
+This function should be called by all stream handlers. It will propagate the early error to the next configured stream handler.
+Arguments StreamID The stream ID.
+ Reason Reason for termination.</description>
+    </item>
+    
+    <item>
       <title>cowboy_stream:info(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.11/manual/cowboy_stream.info/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -9955,6 +11530,18 @@ Arguments StreamID The stream ID.</description>
     </item>
     
     <item>
+      <title>cowboy_stream:info(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.info/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.info/</guid>
+      <description>Name cowboy_stream:info - Handle a message for a stream
+Description info(StreamID, Info, State) -&amp;gt; {Commands, State} StreamID :: cowboy_stream:stream_id() Info :: any() Commands :: cowboy_stream:commands() State - opaque  Handle a message for a stream.
+This function should be called by all stream handlers. It will propagate the event to the next configured stream handler. Handlers do not have to propagate events that have been fully handled.
+Arguments StreamID The stream ID.</description>
+    </item>
+    
+    <item>
       <title>cowboy_stream:init(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.11/manual/cowboy_stream.init/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -9970,6 +11557,21 @@ Arguments StreamID The stream ID.
     </item>
     
     <item>
+      <title>cowboy_stream:init(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.init/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.init/</guid>
+      <description>Name cowboy_stream:init - Initialize a stream
+Description init(StreamID, Req, Opts) -&amp;gt; {Commands, State} StreamID :: cowboy_stream:stream_id() Req :: cowboy_req:req() Opts :: cowboy:opts() Commands :: cowboy_stream:commands() State - opaque  Initialize a stream.
+This function must be called by all stream handlers. It will initialize the next configured stream handler.
+Arguments StreamID The stream ID.
+ Req The Req object.
+ Opts The protocol options.
+ Commands The commands to be executed.</description>
+    </item>
+    
+    <item>
       <title>cowboy_stream:terminate(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.11/manual/cowboy_stream.terminate/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -9985,6 +11587,21 @@ Arguments StreamID The stream ID.
     </item>
     
     <item>
+      <title>cowboy_stream:terminate(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.terminate/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream.terminate/</guid>
+      <description>Name cowboy_stream:terminate - Terminate a stream
+Description terminate(StreamID, Reason, State) -&amp;gt; ok StreamID :: cowboy_stream:stream_id() Reason :: cowboy_stream:reason() State - opaque  Terminate a stream.
+This function must be called by all stream handlers. It will terminate the next configured stream handler.
+Arguments StreamID The stream ID.
+ Reason Reason for termination.
+ State The state for the next stream handler.
+  Return value The atom ok is always returned.</description>
+    </item>
+    
+    <item>
       <title>cowboy_stream_h(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/manual/cowboy_stream_h/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10010,6 +11627,18 @@ The default value is given next to the option name:</description>
     
     <item>
       <title>cowboy_stream_h(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream_h/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_stream_h/</guid>
+      <description>Name cowboy_stream_h - Default stream handler
+Description The module cowboy_stream_h is Cowboy&amp;apos;s default stream handler and defines much of its behavior. It is responsible for managing the request process, sending it the request body and translating its messages into commands that Cowboy understands.
+Options opts() :: #{ env =&amp;gt; cowboy_middleware:env(), middlewares =&amp;gt; [module()], shutdown_timeout =&amp;gt; timeout() }  Configuration for the default stream handler.
+The default value is given next to the option name:</description>
+    </item>
+    
+    <item>
+      <title>cowboy_stream_h(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_stream_h/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -10080,6 +11709,17 @@ Options opts() :: #{ tracer_callback =&amp;gt; Callback, tracer_flags =&amp;gt;
     
     <item>
       <title>cowboy_tracer_h(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_tracer_h/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_tracer_h/</guid>
+      <description>Name cowboy_tracer_h - Tracer stream handler
+Description The module cowboy_tracer_h can be used to conditionally trace streams based on information found in the request. Trace messages are given to the configured callback.
+Options opts() :: #{ tracer_callback =&amp;gt; Callback, tracer_flags =&amp;gt; [atom()], tracer_match_specs =&amp;gt; [MatchSpec] } Callback :: fun((init | terminate | tuple(), State) -&amp;gt; State) MatchSpec :: MatchPredicate | {method, binary()} | {host, binary()} | {path, binary()} | {path_start, binary()} | {header, binary()} | {header, binary(), binary()} | {peer_ip, inet:ip_address()} MatchPredicate :: fun((cowboy_stream:streamid(), cowboy_req:req(), cowboy:opts()) -&amp;gt; boolean()) }  Configuration for the tracer stream handler.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_tracer_h(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_tracer_h/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -10137,6 +11777,18 @@ init(Req, State) -&amp;gt; {cowboy_websocket, Req, State} | {cowboy_websocket, R
     
     <item>
       <title>cowboy_websocket(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_websocket/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/cowboy_websocket/</guid>
+      <description>Name cowboy_websocket - Websocket
+Description The module cowboy_websocket implements Websocket as a Ranch protocol. It also defines a callback interface for handling Websocket connections.
+Callbacks Websocket handlers must implement the following callback interface:
+init(Req, State) -&amp;gt; {cowboy_websocket, Req, State} | {cowboy_websocket, Req, State, Opts} websocket_init(State) -&amp;gt; CallResult %% optional websocket_handle(InFrame, State) -&amp;gt; CallResult websocket_info(Info, State) -&amp;gt; CallResult terminate(Reason, PartialReq, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() PartialReq :: map() State :: any() Opts :: cowboy_websocket:opts() InFrame :: ping | pong | {text | binary | ping | pong, binary()} Info :: any() CallResult :: {commands(), State} | {commands(), State, hibernate} | Deprecated Deprecated :: {ok, State} | {ok, State, hibernate} | {reply, OutFrame | [OutFrame], State} | {reply, OutFrame | [OutFrame], State, hibernate} | {stop, State} OutFrame :: cow_ws:frame() %% see types below Reason :: normal | stop | timeout | remote | {remote, cow_ws:close_code(), binary()} | {error, badencoding | badframe | closed | atom()} | {crash, error | exit | throw, any()}  The init/2 callback is common to all handlers.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_websocket(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_websocket/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -10221,6 +11873,18 @@ Modules cow_cookie(3) - Cookies   Dependencies crypto - Crypto functions   All t
     
     <item>
       <title>Cowlib Function Reference</title>
+      <link>https://ninenines.eu/docs/en/cowlib/2.13/manual/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowlib/2.13/manual/</guid>
+      <description>Name cowlib - Support library for manipulating Web protocols
+Description Cowlib provides libraries for parsing and building messages for various Web protocols, including HTTP/1.1, HTTP/2 and Websocket.
+It is optimized for completeness rather than speed. No value is ignored, they are all returned.
+Modules cow_cookie(3) - Cookies   Dependencies crypto - Crypto functions   All these applications must be started before the cowlib application. To start Cowlib and all dependencies at once:</description>
+    </item>
+    
+    <item>
+      <title>Cowlib Function Reference</title>
       <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -10281,6 +11945,18 @@ Modules cow_cookie(3) - Cookies   Dependencies crypto - Crypto functions   All t
     
     <item>
       <title>cowlib(7)</title>
+      <link>https://ninenines.eu/docs/en/cowlib/2.13/manual/cowlib_app/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowlib/2.13/manual/cowlib_app/</guid>
+      <description>Name cowlib - Support library for manipulating Web protocols
+Description Cowlib provides libraries for parsing and building messages for various Web protocols, including HTTP/1.1, HTTP/2 and Websocket.
+It is optimized for completeness rather than speed. No value is ignored, they are all returned.
+Modules cow_cookie(3) - Cookies   Dependencies crypto - Crypto functions   All these applications must be started before the cowlib application. To start Cowlib and all dependencies at once:</description>
+    </item>
+    
+    <item>
+      <title>cowlib(7)</title>
       <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/cowlib_app/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
@@ -10364,6 +12040,18 @@ Modules gun(3) - Asynchronous HTTP client  gun_cookies(3) - Cookie store engine
     </item>
     
     <item>
+      <title>Gun Function Reference</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/</guid>
+      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
+Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
+Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
+Modules gun(3) - Asynchronous HTTP client  gun_cookies(3) - Cookie store engine  gun_cookies_list(3) - Cookie store backend: in-memory, per connection  gun_event(3) - Events  gun_ws_protocol(3) - Websocket subprotocols   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
+    </item>
+    
+    <item>
       <title>Gun User Guide</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/guide/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10409,6 +12097,15 @@ Modules gun(3) - Asynchronous HTTP client  gun_cookies(3) - Cookie store engine
     </item>
     
     <item>
+      <title>Gun User Guide</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/guide/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/guide/</guid>
+      <description>Interface Introduction  Starting and stopping  Supported protocols  Connection  Using HTTP  Using Websocket   Advanced Internals: TLS over TLS   Additional information Changes since Gun 2.0  Migrating from Gun 1.3 to 2.0  Migrating from Gun 1.2 to 1.3  Migrating from Gun 1.1 to 1.2  Migrating from Gun 1.0 to 1.1   </description>
+    </item>
+    
+    <item>
       <title>gun(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10469,6 +12166,18 @@ gun:open(3) - Open a connection to the given host and port  gun:open_unix(3) - O
     </item>
     
     <item>
+      <title>gun(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun/</guid>
+      <description>Name gun - Asynchronous HTTP client
+Description The gun module provides an asynchronous interface for connecting and communicating with Web servers over HTTP, HTTP/2 or Websocket.
+Exports Connection:
+gun:open(3) - Open a connection to the given host and port  gun:open_unix(3) - Open a connection to the given Unix domain socket  gun:set_owner(3) - Set a new owner for the connection  gun:shutdown(3) - Gracefully close the connection  gun:close(3) - Brutally close the connection  gun:info(3) - Obtain information about the connection   Requests:</description>
+    </item>
+    
+    <item>
       <title>gun(7)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_app/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10529,6 +12238,18 @@ Modules gun(3) - Asynchronous HTTP client  gun_cookies(3) - Cookie store engine
     </item>
     
     <item>
+      <title>gun(7)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_app/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_app/</guid>
+      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
+Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
+Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
+Modules gun(3) - Asynchronous HTTP client  gun_cookies(3) - Cookie store engine  gun_cookies_list(3) - Cookie store backend: in-memory, per connection  gun_event(3) - Events  gun_ws_protocol(3) - Websocket subprotocols   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
+    </item>
+    
+    <item>
       <title>gun:await(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10584,6 +12305,17 @@ This function waits for a message from the given stream and returns it as a tupl
     </item>
     
     <item>
+      <title>gun:await(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.await/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.await/</guid>
+      <description>Name gun:await - Wait for a response
+Description await(ConnPid, StreamRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, MonitorRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, Timeout) -&amp;gt; await(ConnPid, StreamRef, Timeout, MonitorRef) await(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; Result ConnPid :: pid() StreamRef :: gun:stream_ref() MonitorRef :: reference() Timeout :: timeout() Result :: tuple() - see below  Wait for a response.
+This function waits for a message from the given stream and returns it as a tuple.</description>
+    </item>
+    
+    <item>
       <title>gun:await_body(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10634,6 +12366,16 @@ Description await_body(ConnPid, StreamRef) -&amp;gt; await_body(ConnPid, StreamR
     </item>
     
     <item>
+      <title>gun:await_body(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.await_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.await_body/</guid>
+      <description>Name gun:await_body - Wait for the complete response body
+Description await_body(ConnPid, StreamRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, MonitorRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, Timeout) -&amp;gt; await_body(ConnPid, StreamRef, Timeout, MonitorRef) await_body(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; {ok, Body} | {ok, Body, Trailers} | {error, Reason} ConnPid :: pid() StreamRef :: gun:stream_ref() MonitorRef :: reference() Timeout :: timeout() Body :: binary() Trailers :: [{binary(), binary()}] Reason :: {stream_error | connection_error | down, any()} | timeout  Wait for the complete response body.</description>
+    </item>
+    
+    <item>
       <title>gun:await_up(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await_up/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10689,6 +12431,17 @@ Arguments ConnPid The pid of the Gun connection process.</description>
     </item>
     
     <item>
+      <title>gun:await_up(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.await_up/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.await_up/</guid>
+      <description>Name gun:await_up - Wait for the connection to be up
+Description await_up(ConnPid) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, MonitorRef) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, Timeout) -&amp;gt; await_up(ConnPid, Timeout, MonitorRef) await_up(ConnPid, Timeout, MonitorRef) -&amp;gt; {ok, Protocol} | {error, Reason} ConnPid :: pid() MonitorRef :: reference() Timeout :: timeout() Protocol :: http | http2 | socks Reason :: {down, any()} | timeout  Wait for the connection to be up.
+Arguments ConnPid The pid of the Gun connection process.</description>
+    </item>
+    
+    <item>
       <title>gun:cancel(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.cancel/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10749,6 +12502,18 @@ HTTP/1.1 does not support this feature. Gun will simply silence the stream and s
     </item>
     
     <item>
+      <title>gun:cancel(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.cancel/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.cancel/</guid>
+      <description>Name gun:cancel - Cancel the given stream
+Description cancel(ConnPid, StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: gun:stream_ref()  Cancel the given stream.
+The behavior of this function depends on the protocol selected.
+HTTP/1.1 does not support this feature. Gun will simply silence the stream and stop relaying messages. Gun may also decide to close the connection if the response body is too large, to avoid wasting time and bandwidth.</description>
+    </item>
+    
+    <item>
       <title>gun:close(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.close/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10814,6 +12579,19 @@ Changelog 1.0: Function introduced.   Examples Close the connection ok = gun:clo
     </item>
     
     <item>
+      <title>gun:close(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.close/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.close/</guid>
+      <description>Name gun:close - Brutally close the connection
+Description close(ConnPid) -&amp;gt; ok ConnPid :: pid()  Brutally close the connection.
+Arguments ConnPid The pid of the Gun connection process.
+  Return value The atom ok is returned.
+Changelog 1.0: Function introduced.   Examples Close the connection ok = gun:close(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3), gun:shutdown(3)</description>
+    </item>
+    
+    <item>
       <title>gun:connect(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.connect/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10847,6 +12625,17 @@ This feature is currently only available for HTTP/1.1 connections. Upon successf
     </item>
     
     <item>
+      <title>gun:connect(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.connect/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.connect/</guid>
+      <description>Name gun:connect - Establish a tunnel to the origin server
+Description connect(ConnPid, Destination) -&amp;gt; connect(ConnPid, Destination, [], #{}). connect(ConnPid, Destination, Headers) -&amp;gt; connect(ConnPid, Destination, Headers, #{}). connect(ConnPid, Destination, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Destination :: gun:connect_destination() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Establish a tunnel to the origin server.
+This feature is currently only available for HTTP/1.1 connections. Upon successful completion of the CONNECT request a tunnel is established and subsequent requests will go through the tunnel.</description>
+    </item>
+    
+    <item>
       <title>gun:data(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.data/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10907,6 +12696,18 @@ All calls to this function must use the nofin flag except for the last which mus
     </item>
     
     <item>
+      <title>gun:data(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.data/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.data/</guid>
+      <description>Name gun:data - Stream the body of a request
+Description data(ConnPid, StreamRef, IsFin, Data) -&amp;gt; ok ConnPid :: pid() StreamRef :: gun:stream_ref() IsFin :: fin | nofin Data :: iodata()  Stream the body of a request.
+This function can only be used if the original request had headers indicating that a body would be streamed.
+All calls to this function must use the nofin flag except for the last which must use fin to indicate the end of the request body.</description>
+    </item>
+    
+    <item>
       <title>gun:delete(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.delete/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -10977,6 +12778,20 @@ Arguments ConnPid The pid of the Gun connection process.
     </item>
     
     <item>
+      <title>gun:delete(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.delete/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.delete/</guid>
+      <description>Name gun:delete - Delete a resource
+Description delete(ConnPid, Path) -&amp;gt; delete(ConnPid, Path, [], #{}). delete(ConnPid, Path, Headers) -&amp;gt; delete(ConnPid, Path, Headers, #{}) delete(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Delete a resource.
+Arguments ConnPid The pid of the Gun connection process.
+ Path Path to the resource.
+ Headers Additional request headers.
+ ReqOpts Request options.</description>
+    </item>
+    
+    <item>
       <title>gun:flush(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.flush/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11047,6 +12862,20 @@ ConnPid The pid of the Gun connection process.
     </item>
     
     <item>
+      <title>gun:flush(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.flush/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.flush/</guid>
+      <description>Name gun:flush - Flush all messages related to a connection or a stream
+Description flush(ConnPid) -&amp;gt; ok flush(StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: gun:stream_ref()  Flush all messages related to a connection or a stream.
+Arguments Either of these arguments may be provided:
+ConnPid The pid of the Gun connection process.
+ StreamRef Identifier of the stream for the original request.
+  Return value The atom ok is returned.</description>
+    </item>
+    
+    <item>
       <title>gun:get(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.get/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11113,6 +12942,20 @@ Arguments ConnPid The pid of the Gun connection process.
     </item>
     
     <item>
+      <title>gun:get(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.get/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.get/</guid>
+      <description>Name gun:get - Get a resource representation
+Description get(ConnPid, Path) -&amp;gt; get(ConnPid, Path, [], #{}). get(ConnPid, Path, Headers) -&amp;gt; get(ConnPid, Path, Headers, #{}) get(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Get a resource representation.
+Arguments ConnPid The pid of the Gun connection process.
+ Path Path to the resource.
+ Headers Additional request headers.
+ ReqOpts Request options.</description>
+    </item>
+    
+    <item>
       <title>gun:head(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.head/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11168,6 +13011,17 @@ This function performs the same operation as gun:get(3), except the server will
     </item>
     
     <item>
+      <title>gun:head(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.head/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.head/</guid>
+      <description>Name gun:head - Get headers of a resource representation
+Description head(ConnPid, Path) -&amp;gt; head(ConnPid, Path, [], #{}). head(ConnPid, Path, Headers) -&amp;gt; head(ConnPid, Path, Headers, #{}) head(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Get headers of a resource representation.
+This function performs the same operation as gun:get(3), except the server will not send the resource representation, only the response&amp;apos;s status code and headers.</description>
+    </item>
+    
+    <item>
       <title>gun:headers(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.headers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11180,6 +13034,18 @@ The function headers/4,5 initiates a request but does not send the request body.
     </item>
     
     <item>
+      <title>gun:headers(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.headers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.headers/</guid>
+      <description>Name gun:headers - Initiate the given request
+Description headers(ConnPid, Method, Path, Headers) -&amp;gt; headers(ConnPid, Method, Path, Headers, #{}) headers(ConnPid, Method, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Method :: binary() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Initiate the given request.
+This is a general purpose function that should only be used when other method-specific functions do not apply.
+The function headers/4,5 initiates a request but does not send the request body.</description>
+    </item>
+    
+    <item>
       <title>gun:info(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.info/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11239,6 +13105,16 @@ Description info(ConnPid) -&amp;gt; Info ConnPid :: pid() Info :: #{ owner =&amp
     </item>
     
     <item>
+      <title>gun:info(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.info/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.info/</guid>
+      <description>Name gun:info - Obtain information about the connection
+Description info(ConnPid) -&amp;gt; Info ConnPid :: pid() Info :: #{ owner =&amp;gt; pid(), socket =&amp;gt; inet:socket() | ssl:sslsocket(), transport =&amp;gt; tcp | tls, protocol =&amp;gt; http | http2 | socks | ws, sock_ip =&amp;gt; inet:ip_address(), sock_port =&amp;gt; inet:port_number(), origin_scheme =&amp;gt; binary() | undefined, origin_host =&amp;gt; inet:hostname() | inet:ip_address(), origin_port =&amp;gt; inet:port_number(), intermediaries =&amp;gt; [Intermediary], cookie_store =&amp;gt; gun_cookies:cookie_store() } Intermediary :: #{ type =&amp;gt; connect | socks5, host =&amp;gt; inet:hostname() | inet:ip_address(), port =&amp;gt; inet:port_number(), transport =&amp;gt; tcp | tls, protocol =&amp;gt; http | http2 | socks | raw }  Obtain information about the connection.</description>
+    </item>
+    
+    <item>
       <title>gun:open(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.open/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11302,6 +13178,17 @@ Arguments Host Host or IP address to connect to.</description>
     </item>
     
     <item>
+      <title>gun:open(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.open/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.open/</guid>
+      <description>Name gun:open - Open a connection to the given host and port
+Description open(Host, Port) -&amp;gt; open(Host, Port, #{}) open(Host, Port, Opts) -&amp;gt; {ok, pid()} | {error, Reason} Host :: inet:hostname() | inet:ip_address() Port :: inet:port_number() Opts :: gun:opts() Reason :: {options, OptName} | {options, {http | http2 | socks | ws, OptName}} | any() OptName :: atom()  Open a connection to the given host and port.
+Arguments Host Host or IP address to connect to.</description>
+    </item>
+    
+    <item>
       <title>gun:open_unix(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.open_unix/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11366,6 +13253,18 @@ Arguments SocketPath Path to the Unix domain socket to connect to.
     </item>
     
     <item>
+      <title>gun:open_unix(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.open_unix/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.open_unix/</guid>
+      <description>Name gun:open_unix - Open a connection to the given Unix domain socket
+Description open_unix(SocketPath, Opts) -&amp;gt; {ok, pid()} | {error, Reason} SocketPath :: string() Opts :: gun:opts() Reason :: {options, OptName} | {options, {http | http2 | socks | ws, OptName}} | any() OptName :: atom()  Open a connection to the given Unix domain socket.
+Arguments SocketPath Path to the Unix domain socket to connect to.
+ Opts Options for this connection.</description>
+    </item>
+    
+    <item>
       <title>gun:options(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.options/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11421,6 +13320,17 @@ The special path &amp;quot;*&amp;quot; can be used to obtain information about t
     </item>
     
     <item>
+      <title>gun:options(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.options/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.options/</guid>
+      <description>Name gun:options - Query the capabilities of the server or a resource
+Description options(ConnPid, Path) -&amp;gt; options(ConnPid, Path, [], #{}). options(ConnPid, Path, Headers) -&amp;gt; options(ConnPid, Path, Headers, #{}) options(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Query the capabilities of the server or a resource.
+The special path &amp;quot;*&amp;quot; can be used to obtain information about the server as a whole.</description>
+    </item>
+    
+    <item>
       <title>gun:patch(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.patch/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11475,6 +13385,16 @@ Description patch(ConnPid, Path, Headers) -&amp;gt; patch(ConnPid, Path, Headers
     </item>
     
     <item>
+      <title>gun:patch(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.patch/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.patch/</guid>
+      <description>Name gun:patch - Apply a set of changes to a resource
+Description patch(ConnPid, Path, Headers) -&amp;gt; patch(ConnPid, Path, Headers, #{}) patch(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef patch(ConnPid, Path, Headers, Body) -&amp;gt; patch(ConnPid, Path, Headers, Body, #{}) patch(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Apply a set of changes to a resource.</description>
+    </item>
+    
+    <item>
       <title>gun:post(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.post/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11529,6 +13449,16 @@ Description post(ConnPid, Path, Headers) -&amp;gt; post(ConnPid, Path, Headers,
     </item>
     
     <item>
+      <title>gun:post(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.post/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.post/</guid>
+      <description>Name gun:post - Process the enclosed representation according to a resource&amp;apos;s own semantics
+Description post(ConnPid, Path, Headers) -&amp;gt; post(ConnPid, Path, Headers, #{}) post(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef post(ConnPid, Path, Headers, Body) -&amp;gt; post(ConnPid, Path, Headers, Body, #{}) post(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Process the enclosed representation according to a resource&amp;apos;s own semantics.</description>
+    </item>
+    
+    <item>
       <title>gun:put(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.put/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11588,6 +13518,17 @@ The behavior of this function varies depending on whether a body is provided.</d
     </item>
     
     <item>
+      <title>gun:put(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.put/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.put/</guid>
+      <description>Name gun:put - Create or replace a resource
+Description put(ConnPid, Path, Headers) -&amp;gt; put(ConnPid, Path, Headers, #{}) put(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef put(ConnPid, Path, Headers, Body) -&amp;gt; put(ConnPid, Path, Headers, Body, #{}) put(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Create or replace a resource.
+The behavior of this function varies depending on whether a body is provided.</description>
+    </item>
+    
+    <item>
       <title>gun:request(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.request/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11643,6 +13584,17 @@ This is a general purpose function that should only be used when other method-sp
     </item>
     
     <item>
+      <title>gun:request(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.request/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.request/</guid>
+      <description>Name gun:request - Perform the given request
+Description request(ConnPid, Method, Path, Headers, Body) -&amp;gt; request(ConnPid, Method, Path, Headers, Body, #{}) request(ConnPid, Method, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Method :: binary() Path :: iodata() Headers :: gun:req_headers() Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: gun:stream_ref()  Perform the given request.
+This is a general purpose function that should only be used when other method-specific functions do not apply.</description>
+    </item>
+    
+    <item>
       <title>gun:set_owner(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.set_owner/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11657,6 +13609,20 @@ Arguments ConnPid The pid of the Gun connection process.
     </item>
     
     <item>
+      <title>gun:set_owner(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.set_owner/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.set_owner/</guid>
+      <description>Name gun:set_owner - Set a new owner for the connection
+Description set_owner(ConnPid, OwnerPid) -&amp;gt; ok ConnPid :: pid() OwnerPid :: pid()  Set a new owner for the connection.
+Only the current owner of the connection can set a new owner.
+Gun monitors the owner of the connection and automatically shuts down gracefully when the owner exits.
+Arguments ConnPid The pid of the Gun connection process.
+ OwnerPid The pid of the new owner for the connection.</description>
+    </item>
+    
+    <item>
       <title>gun:shutdown(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.shutdown/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11669,6 +13635,18 @@ For HTTP/1.1 there is no such mechanism and Gun will close the connection once t
     </item>
     
     <item>
+      <title>gun:shutdown(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.shutdown/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.shutdown/</guid>
+      <description>Name gun:shutdown - Gracefully close the connection
+Description shutdown(ConnPid) -&amp;gt; ok ConnPid :: pid()  Gracefully close the connection.
+Gun will wait for up to closing_timeout milliseconds before brutally closing the connection. The graceful shutdown mechanism varies between the different protocols:
+For HTTP/1.1 there is no such mechanism and Gun will close the connection once the current response is received. Any pipelined requests are immediately terminated.  For HTTP/2 Gun will send a GOAWAY frame and wait for the existing streams to terminate.</description>
+    </item>
+    
+    <item>
       <title>gun:stream_info(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.stream_info/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11679,6 +13657,16 @@ Description stream_info(ConnPid, StreamRef) -&amp;gt; {ok, undefined | Info} | {
     </item>
     
     <item>
+      <title>gun:stream_info(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.stream_info/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.stream_info/</guid>
+      <description>Name gun:stream_info - Obtain information about a stream
+Description stream_info(ConnPid, StreamRef) -&amp;gt; {ok, undefined | Info} | {error, not_connected} ConnPid :: pid() StreamRef :: gun:stream_ref() Info :: #{ ref =&amp;gt; gun:stream_ref(), reply_to =&amp;gt; pid(), state =&amp;gt; running | stopping, intermediaries =&amp;gt; [Intermediary], tunnel =&amp;gt; Tunnel } Intermediary :: #{ type =&amp;gt; connect | socks5, host =&amp;gt; inet:hostname() | inet:ip_address(), port =&amp;gt; inet:port_number(), transport =&amp;gt; tcp | tls, protocol =&amp;gt; http | http2 | socks | raw } Tunnel :: #{ transport =&amp;gt; tcp | tls, protocol =&amp;gt; http | http2 | socks | raw, origin_scheme =&amp;gt; binary() | undefined, origin_host =&amp;gt; inet:hostname() | inet:ip_address(), origin_port =&amp;gt; inet:port_number() }  Obtain information about a stream.</description>
+    </item>
+    
+    <item>
       <title>gun:update_flow(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.update_flow/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11693,6 +13681,20 @@ Arguments ConnPid The pid of the Gun connection process.
     </item>
     
     <item>
+      <title>gun:update_flow(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.update_flow/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.update_flow/</guid>
+      <description>Name gun:update_flow - Update a stream&amp;apos;s flow control value
+Description update_flow(ConnPid, StreamRef, Flow) -&amp;gt; ok ConnPid :: pid() StreamRef :: gun:stream_ref() Flow :: pos_integer()  Update a stream&amp;apos;s flow control value.
+The flow value can only ever be incremented.
+This function does nothing for streams that have flow control disabled (which is the default).
+Arguments ConnPid The pid of the Gun connection process.
+ StreamRef Identifier of the stream for the original request.</description>
+    </item>
+    
+    <item>
       <title>gun:ws_send(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.ws_send/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11757,6 +13759,18 @@ Arguments ConnPid The pid of the Gun connection process.</description>
     </item>
     
     <item>
+      <title>gun:ws_send(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.ws_send/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.ws_send/</guid>
+      <description>Name gun:ws_send - Send Websocket frames
+Description ws_send(ConnPid, StreamRef, Frames) -&amp;gt; ok ConnPid :: pid() StreamRef :: gun:stream_ref() Frames :: Frame | [Frame] Frame :: close | ping | pong | {text | binary | close | ping | pong, iodata()} | {close, non_neg_integer(), iodata()}  Send Websocket frames.
+The connection must first be upgraded to Websocket using the function gun:ws_upgrade(3).
+Arguments ConnPid The pid of the Gun connection process.</description>
+    </item>
+    
+    <item>
       <title>gun:ws_upgrade(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.ws_upgrade/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11817,6 +13831,18 @@ HTTP/1.1 cannot handle Websocket and HTTP requests concurrently. The upgrade, if
     </item>
     
     <item>
+      <title>gun:ws_upgrade(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun.ws_upgrade/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun.ws_upgrade/</guid>
+      <description>Name gun:ws_upgrade - Upgrade to Websocket
+Description ws_upgrade(ConnPid, Path) -&amp;gt; ws_upgrade(ConnPid, Path, []) ws_upgrade(ConnPid, Path, Headers) -&amp;gt; StreamRef ws_upgrade(ConnPid, Path, Headers, WsOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() WsOpts :: gun:ws_opts() StreamRef :: gun:stream_ref()  Upgrade to Websocket.
+The behavior of this function depends on the protocol selected.
+HTTP/1.1 cannot handle Websocket and HTTP requests concurrently. The upgrade, if successful, will result in the complete takeover of the connection.</description>
+    </item>
+    
+    <item>
       <title>gun_cookies(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_cookies/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11829,6 +13855,18 @@ init init(Opts :: any()) -&amp;gt; gun_cookies:store()  Initialize the cookie st
     </item>
     
     <item>
+      <title>gun_cookies(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_cookies/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_cookies/</guid>
+      <description>Name gun_cookies - Cookie store engine
+Description The gun_cookies module implements a cookie store engine. It will be used by Gun when a cookie store is configured. It also defines the interface and provides functions used to implement cookie store backends.
+Callbacks Cookie store backends implement the following interface. Functions are organized by theme: initialization, querying, storing and garbage collecting:
+init init(Opts :: any()) -&amp;gt; gun_cookies:store()  Initialize the cookie store.</description>
+    </item>
+    
+    <item>
       <title>gun_cookies:domain_match(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_cookies.domain_match/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11844,6 +13882,21 @@ Changelog 2.0: Function introduced.   Examples Perform a domain match Match = gu
     </item>
     
     <item>
+      <title>gun_cookies:domain_match(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_cookies.domain_match/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_cookies.domain_match/</guid>
+      <description>Name gun_cookies:domain_match - Cookie domain match
+Description domain_match(String, DomainString) -&amp;gt; boolean() String :: binary() DomainString :: binary()  Cookie domain match.
+This function can be used when implementing the set_cookie_secure_match callback of a cookie store.
+Arguments String The string to match.
+ DomainString The domain string that will be matched against.
+  Return value Returns true when String domain-matches DomainString, and false otherwise.
+Changelog 2.0: Function introduced.   Examples Perform a domain match Match = gun_cookies:domain_match(Domain, CookieDomain).</description>
+    </item>
+    
+    <item>
       <title>gun_cookies:path_match(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_cookies.path_match/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11859,6 +13912,21 @@ Changelog 2.0: Function introduced.   Examples Perform a path match Match = gun_
     </item>
     
     <item>
+      <title>gun_cookies:path_match(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_cookies.path_match/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_cookies.path_match/</guid>
+      <description>Name gun_cookies:path_match - Cookie path match
+Description path_match(ReqPath, CookiePath) -&amp;gt; boolean() ReqPath :: binary() CookiePath :: binary()  Cookie path match.
+This function can be used when implementing the set_cookie_secure_match callback of a cookie store.
+Arguments ReqPath The request path to match.
+ CookiePath The cookie path that will be matched against.
+  Return value Returns true when ReqPath path-matches CookiePath, and false otherwise.
+Changelog 2.0: Function introduced.   Examples Perform a path match Match = gun_cookies:path_match(ReqPath, CookiePath).</description>
+    </item>
+    
+    <item>
       <title>gun_cookies_list(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_cookies_list/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11872,6 +13940,19 @@ Types opts() opts() :: #{ }  Cookie store backend options.</description>
     </item>
     
     <item>
+      <title>gun_cookies_list(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_cookies_list/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_cookies_list/</guid>
+      <description>Name gun_cookies_list - Cookie store backend: in-memory, per connection
+Description The gun_cookies_list module implements a cookie store backend that keeps all the cookie data in-memory and tied to a specific connection.
+It is possible to implement a custom backend on top of gun_cookies_list in order to add persistence or sharing properties.
+Exports This module implements the callbacks defined in gun_cookies(3).
+Types opts() opts() :: #{ }  Cookie store backend options.</description>
+    </item>
+    
+    <item>
       <title>gun_data(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_data/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11937,6 +14018,19 @@ The response body may be terminated either by a data message with the flag fin s
     </item>
     
     <item>
+      <title>gun_data(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_data/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_data/</guid>
+      <description>Name gun_data - Response body
+Description {gun_data, ConnPid, StreamRef, IsFin, Data} ConnPid :: pid() StreamRef :: gun:stream_ref() IsFin :: fin | nofin Data :: binary()  Response body.
+This message informs the relevant process that the server sent a all or part of the body for the response to the original request.
+A data message is always preceded by a response message.
+The response body may be terminated either by a data message with the flag fin set or by a gun_trailers(3) message.</description>
+    </item>
+    
+    <item>
       <title>gun_down(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_down/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -11997,6 +14091,18 @@ When the connection goes back up, Gun will not attempt to retry requests.</descr
     </item>
     
     <item>
+      <title>gun_down(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_down/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_down/</guid>
+      <description>Name gun_down - The connection is down
+Description {gun_down, ConnPid, Protocol, Reason, KilledStreams} ConnPid :: pid() Protocol :: http | http2 | socks | ws Reason :: any() KilledStreams :: [gun:stream_ref()]  The connection is down.
+This message informs the owner process that the connection was lost. Depending on the retry and retry_timeout options Gun may automatically attempt to reconnect.
+When the connection goes back up, Gun will not attempt to retry requests.</description>
+    </item>
+    
+    <item>
       <title>gun_error(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_error/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12052,6 +14158,17 @@ These messages inform the relevant process that an error occurred. A reference i
     </item>
     
     <item>
+      <title>gun_error(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_error/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_error/</guid>
+      <description>Name gun_error - Stream or connection-wide error
+Description {gun_error, ConnPid, StreamRef, Reason} {gun_error, ConnPid, Reason} ConnPid :: pid() StreamRef :: gun:stream_ref() Reason :: any()  Stream or connection-wide error.
+These messages inform the relevant process that an error occurred. A reference is given when the error pertains to a specific stream. Connection-wide errors do not imply that the connection is no longer usable, they are used for all errors that are not specific to a stream.</description>
+    </item>
+    
+    <item>
       <title>gun_event(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_event/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12065,6 +14182,19 @@ init init_event() :: #{ owner := pid(), transport := tcp | tls, origin_scheme :=
     </item>
     
     <item>
+      <title>gun_event(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_event/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_event/</guid>
+      <description>Name gun_event - Events
+Description The gun_event module provides the callback interface and types for implementing event handlers.
+Callbacks Event handlers implement the following interface. Because types are tied to specific events, they are documented alongside them. All event types are exported and can be referred to as gun_event:Type().
+The events are ordered by the order they are likely to be triggered, with the most frequent events listed first.
+init init_event() :: #{ owner := pid(), transport := tcp | tls, origin_scheme := binary(), origin_host := inet:hostname() | inet:ip_address(), origin_port := inet:port_number(), opts := gun:opts() } init(init_event(), State) -&amp;gt; State  Gun is initializing.</description>
+    </item>
+    
+    <item>
       <title>gun_inform(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_inform/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12125,6 +14255,18 @@ Informational responses are only intermediate responses and provide no guarantee
     </item>
     
     <item>
+      <title>gun_inform(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_inform/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_inform/</guid>
+      <description>Name gun_inform - Informational response
+Description {gun_inform, ConnPid, StreamRef, Status, Headers} ConnPid :: pid() StreamRef :: gun:stream_ref() Status :: 100..199 Headers :: [{binary(), binary()}]  Informational response.
+This message informs the relevant process that the server sent an informational response to the original request.
+Informational responses are only intermediate responses and provide no guarantees as to what the final response will be. An informational response always precedes the response to the original request.</description>
+    </item>
+    
+    <item>
       <title>gun_push(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_push/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12185,6 +14327,18 @@ A server-initiated push message always precedes the response to the original req
     </item>
     
     <item>
+      <title>gun_push(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_push/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_push/</guid>
+      <description>Name gun_push - Server-initiated push
+Description {gun_push, ConnPid, StreamRef, NewStreamRef, Method, URI, Headers} ConnPid :: pid() StreamRef :: gun:stream_ref() NewStreamRef :: gun:stream_ref() Method :: binary() URI :: binary() Headers :: [{binary(), binary()}]  Server-initiated push.
+This message informs the relevant process that the server is pushing a resource related to the effective target URI of the original request.
+A server-initiated push message always precedes the response to the original request.</description>
+    </item>
+    
+    <item>
       <title>gun_response(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_response/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12255,6 +14409,20 @@ Elements ConnPid The pid of the Gun connection process.
     </item>
     
     <item>
+      <title>gun_response(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_response/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_response/</guid>
+      <description>Name gun_response - Response
+Description {gun_response, ConnPid, StreamRef, IsFin, Status, Headers} ConnPid :: pid() StreamRef :: gun:stream_ref() IsFin :: fin | nofin Status :: non_neg_integer() Headers :: [{binary(), binary()}]  Response.
+This message informs the relevant process that the server sent a response to the original request.
+Elements ConnPid The pid of the Gun connection process.
+ StreamRef Identifier of the stream for the original request.
+ IsFin Whether this message terminates the response.</description>
+    </item>
+    
+    <item>
       <title>gun_trailers(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_trailers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12330,6 +14498,21 @@ Elements ConnPid The pid of the Gun connection process.
     </item>
     
     <item>
+      <title>gun_trailers(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_trailers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_trailers/</guid>
+      <description>Name gun_trailers - Response trailers
+Description {gun_trailers, ConnPid, StreamRef, Headers} ConnPid :: pid() StreamRef :: gun:stream_ref() Headers :: [{binary(), binary()}]  Response trailers.
+This message informs the relevant process that the server sent response trailers for the response to the original request.
+A trailers message terminates the response.
+Elements ConnPid The pid of the Gun connection process.
+ StreamRef Identifier of the stream for the original request.
+ Headers Trailing headers sent after the response body.</description>
+    </item>
+    
+    <item>
       <title>gun_tunnel_up(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_tunnel_up/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12342,6 +14525,18 @@ If Gun is configured to connect to another SOCKS server, then the connection is
     </item>
     
     <item>
+      <title>gun_tunnel_up(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_tunnel_up/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_tunnel_up/</guid>
+      <description>Name gun_tunnel_up - The tunnel is up
+Description {gun_tunnel_up, ConnPid, StreamRef, Protocol} ConnPid :: pid() StreamRef :: gun:stream_ref() | undefined Protocol :: http | http2 | socks  The tunnel is up.
+This message informs the owner/calling process that the connection completed through the SOCKS or CONNECT proxy.
+If Gun is configured to connect to another SOCKS server, then the connection is not usable yet. One or more gun_tunnel_up(3) messages will follow.</description>
+    </item>
+    
+    <item>
       <title>gun_up(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_up/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12403,6 +14598,19 @@ Otherwise, Gun will start processing the messages it received while waiting for
     </item>
     
     <item>
+      <title>gun_up(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_up/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_up/</guid>
+      <description>Name gun_up - The connection is up
+Description {gun_up, ConnPid, Protocol} ConnPid :: pid() Protocol :: http | http2 | raw | socks  The connection is up.
+This message informs the owner process that the connection or reconnection completed.
+If Gun is configured to connect to a Socks server, then the connection is not usable yet. One or more gun_tunnel_up(3) messages will follow.
+Otherwise, Gun will start processing the messages it received while waiting for the connection to be up.</description>
+    </item>
+    
+    <item>
       <title>gun_upgrade(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_upgrade/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12463,6 +14671,18 @@ The exact semantics of this message depend on the original protocol. HTTP/1.1 up
     </item>
     
     <item>
+      <title>gun_upgrade(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_upgrade/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_upgrade/</guid>
+      <description>Name gun_upgrade - Successful protocol upgrade
+Description {gun_upgrade, ConnPid, StreamRef, Protocols, Headers} ConnPid :: pid() StreamRef :: gun:stream_ref() Protocols :: [&amp;lt;&amp;lt;&#34;websocket&#34;&amp;gt;&amp;gt;] Headers :: [{binary(), binary()}]  Successful protocol upgrade.
+This message informs the relevant process that the server accepted to upgrade to one or more protocols given in the original request.
+The exact semantics of this message depend on the original protocol. HTTP/1.1 upgrades apply to the entire connection. HTTP/2 uses a different mechanism which allows switching specific streams to a different protocol.</description>
+    </item>
+    
+    <item>
       <title>gun_ws(3)</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_ws/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12527,6 +14747,18 @@ This message can only be sent on streams that were upgraded to the Websocket pro
     </item>
     
     <item>
+      <title>gun_ws(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_ws/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_ws/</guid>
+      <description>Name gun_ws - Websocket frame
+Description {gun_ws, ConnPid, StreamRef, Frame} ConnPid :: pid() StreamRef :: gun:stream_ref() Frame :: close | ping | pong | {text | binary | close, binary()} | {close, non_neg_integer(), binary()} | {ping | pong, binary()}  Websocket frame.
+This message informs the relevant process that the server sent the enclosed frame.
+This message can only be sent on streams that were upgraded to the Websocket protocol.</description>
+    </item>
+    
+    <item>
       <title>gun_ws_protocol(3)</title>
       <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_ws_protocol/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12540,6 +14772,19 @@ ReplyTo The pid of the process that owns the stream and to which messages will b
     </item>
     
     <item>
+      <title>gun_ws_protocol(3)</title>
+      <link>https://ninenines.eu/docs/en/gun/2.1/manual/gun_ws_protocol/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/gun/2.1/manual/gun_ws_protocol/</guid>
+      <description>Name gun_ws_protocol - Websocket subprotocols
+Description The gun_ws_protocol module provides the callback interface and types for implementing Websocket subprotocols.
+Callbacks Websocket subprotocols implement the following interface.
+init init(ReplyTo, StreamRef, Headers, Opts) -&amp;gt; {ok, State} ReplyTo :: pid() StreamRef :: reference() Headers :: cow_http:headers() Opts :: gun:ws_opts() State :: protocol_state()  Initialize the Websocket protocol.
+ReplyTo The pid of the process that owns the stream and to which messages will be sent to.</description>
+    </item>
+    
+    <item>
       <title>HTTP status codes(7)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.10/manual/http_status_codes/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -12563,6 +14808,17 @@ Description This chapter aims to list all HTTP status codes that Cowboy may retu
     
     <item>
       <title>HTTP status codes(7)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.12/manual/http_status_codes/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.12/manual/http_status_codes/</guid>
+      <description>Name HTTP status codes - status codes used by Cowboy
+Description This chapter aims to list all HTTP status codes that Cowboy may return, with details on the reasons why. The list given here only includes the replies that Cowboy sends, not user replies.
+100 Continue When the client sends an expect: 100-continue header, Cowboy automatically sends a this status code before trying to read the request body. This behavior can be disabled using the appropriate body option.</description>
+    </item>
+    
+    <item>
+      <title>HTTP status codes(7)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/http_status_codes/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>