Cowboy 2.4.0

author: Loïc Hoguin <[email protected]> 2018-05-02 11:35:26 +0200
committer: Loïc Hoguin <[email protected]> 2018-05-02 11:35:26 +0200
commit: fec98300ec9af6c8b5f3120a60f217983c451076 (patch)
tree: 9772977293124e8b9b5b253e44d8c2695cddfb44 /index.xml
parent: bfd2b6e01cbb36b0be0b3c860f5baf8d5b49fe7a (diff)
download: ninenines.eu-fec98300ec9af6c8b5f3120a60f217983c451076.tar.gz
ninenines.eu-fec98300ec9af6c8b5f3120a60f217983c451076.tar.bz2
ninenines.eu-fec98300ec9af6c8b5f3120a60f217983c451076.zip
1 files changed, 1155 insertions, 3 deletions
diff --git a/index.xml b/index.xml
index f8fc609e..de7652ea 100644
--- a/index.xml
+++ b/index.xml
@@ -6,7 +6,7 @@
     <description>Recent content on Nine Nines</description>
     <generator>Hugo -- gohugo.io</generator>
     <language>en-us</language>
-    <lastBuildDate>Wed, 04 Apr 2018 12:00:00 +0100</lastBuildDate>
+    <lastBuildDate>Wed, 02 May 2018 10:00:00 +0100</lastBuildDate>
     
 	<atom:link href="https://ninenines.eu/index.xml" rel="self" type="application/rss+xml" />
     
@@ -116,6 +116,17 @@
     </item>
     
     <item>
+      <title>The modern Web</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/modern_web/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>Erlang and the Web</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/guide/erlang_web/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -156,6 +167,16 @@
     </item>
     
     <item>
+      <title>Erlang and the Web</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/erlang_web/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Getting started</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/getting_started/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -268,6 +289,18 @@
     </item>
     
     <item>
+      <title>Introduction</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/introduction/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Transports</title>
       <link>https://ninenines.eu/docs/en/ranch/1.2/guide/transports/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -398,6 +431,16 @@
     </item>
     
     <item>
+      <title>Getting started</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/getting_started/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Updating Erlang.mk</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/updating/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -507,6 +550,17 @@
     </item>
     
     <item>
+      <title>Flow diagram</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/flow_diagram/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>Websocket</title>
       <link>https://ninenines.eu/docs/en/gun/1.0/guide/websocket/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -607,6 +661,17 @@
     </item>
     
     <item>
+      <title>Listeners</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/listeners/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>SSL client authentication</title>
       <link>https://ninenines.eu/docs/en/ranch/1.2/guide/ssl_auth/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -696,6 +761,18 @@
     </item>
     
     <item>
+      <title>Routing</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/routing/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.
+ When Cowboy receives a request, it tries to match the requested host and path to the configured routes. When there&amp;#8217;s a match, the route&amp;#8217;s associated handler is executed.
+ Routes need to be compiled before they can be used by Cowboy. The result of the compilation is the dispatch rules.</description>
+    </item>
+    
+    <item>
       <title>NIFs and port drivers</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/ports/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -785,6 +862,18 @@
     </item>
     
     <item>
+      <title>Constraints</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/constraints/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Releases</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/releases/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -860,6 +949,19 @@
     </item>
     
     <item>
+      <title>Handlers</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/handlers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Escripts</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/escripts/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -912,6 +1014,16 @@
     </item>
     
     <item>
+      <title>Loop handlers</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/loop_handlers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>OTP version management</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/kerl/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -966,6 +1078,17 @@
     </item>
     
     <item>
+      <title>Static files</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/static_files/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Compatibility with other build tools</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/compat/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1031,6 +1154,17 @@
     </item>
     
     <item>
+      <title>The Req object</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/req/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Reading the request body</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/guide/req_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1079,6 +1213,18 @@
     </item>
     
     <item>
+      <title>Reading the request body</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/req_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>EDoc comments</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/edoc/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1146,6 +1292,17 @@
     </item>
     
     <item>
+      <title>Sending a response</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/resp/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>Erlang shell</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/shell/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1197,6 +1354,16 @@
     </item>
     
     <item>
+      <title>Using cookies</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/cookies/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>EUnit</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/eunit/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1252,6 +1419,17 @@
     </item>
     
     <item>
+      <title>Multipart requests</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/multipart/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Common Test</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/common_test/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1307,6 +1485,17 @@
     </item>
     
     <item>
+      <title>REST principles</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_principles/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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;#8217;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>Code coverage</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/coverage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1361,6 +1550,17 @@
     </item>
     
     <item>
+      <title>REST handlers</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_handlers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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;#8217;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.</description>
+    </item>
+    
+    <item>
       <title>Continuous integration</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/ci/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1426,6 +1626,17 @@
     </item>
     
     <item>
+      <title>REST flowcharts</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_flowcharts/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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 &#34;Start&#34; diagram, and all paths excluding the OPTIONS path go through the &#34;Content negotiation&#34;</description>
+    </item>
+    
+    <item>
       <title>Xref</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/xref/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1476,6 +1687,16 @@
     </item>
     
     <item>
+      <title>Designing a resource handler</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/resource_design/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>External plugins</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/external_plugins/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1531,6 +1752,17 @@
     </item>
     
     <item>
+      <title>The Websocket protocol</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/ws_protocol/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>List of plugins</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/external_plugins_list/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1584,6 +1816,16 @@
     </item>
     
     <item>
+      <title>Websocket handlers</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/ws_handlers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Why Erlang.mk</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/why/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1640,6 +1882,17 @@
     </item>
     
     <item>
+      <title>Streams</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/streams/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Short history</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/history/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1695,6 +1948,17 @@
     </item>
     
     <item>
+      <title>Middlewares</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/middlewares/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Contributing</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/contributing/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1748,6 +2012,16 @@
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.3 to 2.4</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.3/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.0/guide/specs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1789,6 +2063,16 @@
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.2 to 2.3</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.2/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>HTTP and other specifications</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.1/guide/specs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1819,6 +2103,16 @@
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.1 to 2.2</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.1/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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>Migrating from Cowboy 1.0 to 2.0</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1841,6 +2135,16 @@
     </item>
     
     <item>
+      <title>Migrating from Cowboy 2.0 to 2.1</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.0/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>HTTP and other specifications</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/specs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -1861,6 +2165,38 @@
     </item>
     
     <item>
+      <title>Migrating from Cowboy 1.0 to 2.0</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_1.0/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
+      <title>HTTP and other specifications</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/specs/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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;#8217;s Dissertation    RFC 1945: HTTP/1.</description>
+    </item>
+    
+    <item>
+      <title>Cowboy 2.4</title>
+      <link>https://ninenines.eu/articles/cowboy-2.4.0/</link>
+      <pubDate>Wed, 02 May 2018 10:00:00 +0100</pubDate>
+      
+      <guid>https://ninenines.eu/articles/cowboy-2.4.0/</guid>
+      <description>Cowboy 2.4.0 has been released!
+ Numerous HTTP/2 options have been added to control the HTTP/2 SETTINGS and general behavior of HTTP/2 connections. The options for initial window sizes, maximum frame sizes or compression table sizes might be of interest for optimizing the performance of HTTP/2 connections.
+ Experimental support for Websocket over HTTP/2 was added. Note that browsers do not currently support it. The only browser with partial support is Google Chrome 67 (dev build) started with a specific flag.</description>
+    </item>
+    
+    <item>
       <title>Cowboy 2.3</title>
       <link>https://ninenines.eu/articles/cowboy-2.3.0/</link>
       <pubDate>Wed, 04 Apr 2018 12:00:00 +0100</pubDate>
@@ -2290,6 +2626,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>Cowboy Function Reference</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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 User Guide</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/guide/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2326,6 +2675,15 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>Cowboy User Guide</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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     Additional information    Migrating from Cowboy 2.</description>
+    </item>
+    
+    <item>
       <title>Erlang.mk User Guide</title>
       <link>https://ninenines.eu/docs/en/erlang.mk/1/guide/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2397,6 +2755,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>HTTP status codes(7)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/http_status_codes/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>Ranch Function Reference</title>
       <link>https://ninenines.eu/docs/en/ranch/1.2/manual/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2495,6 +2864,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:set_env(3) - Update a listener&amp;#8217;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(7)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_app/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2547,6 +2927,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy(7)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_app/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:set_env(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy.set_env/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2599,6 +2992,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy:set_env(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.set_env/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.set_env/</guid>
+      <description>Name cowboy:set_env - Update a listener&amp;#8217;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:start_clear(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy.start_clear/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2643,6 +3049,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy:start_clear(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.start_clear/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy:start_tls(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy.start_tls/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2691,6 +3108,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy:start_tls(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.start_tls/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:stop_listener(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy.stop_listener/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2743,6 +3172,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy:stop_listener(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.stop_listener/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_constraints(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_constraints/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2795,6 +3237,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_constraints(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:int(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_constraints.int/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2847,6 +3302,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_constraints:int(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints.int/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:nonempty(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_constraints.nonempty/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2903,6 +3371,20 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_constraints:nonempty(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints.nonempty/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_handler(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_handler/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2951,6 +3433,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_handler(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_handler/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:terminate(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_handler.terminate/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -2999,6 +3493,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_handler:terminate(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_handler.terminate/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_http(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_http/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3043,6 +3549,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_http(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_http/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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() :: #{ connection_type =&amp;gt; worker | supervisor, env =&amp;gt; cowboy_middleware:env(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), 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(), middlewares =&amp;gt; [module()], request_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] } Configuration for the HTTP/1.</description>
+    </item>
+    
+    <item>
       <title>cowboy_http2(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_http2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3089,8 +3606,20 @@ Crowdfund my salary or buy The Erlanger Playbook
       <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_http2/</guid>
       <description>Name cowboy_http2 - HTTP/2
    Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
-   Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, enable_connect_protocol =&amp;gt; boolean(), env =&amp;gt; cowboy_middleware:env(), inactivity_timeout =&amp;gt; timeout(), middlewares =&amp;gt; [module()], preface_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] } Configuration for the HTTP/2 protocol.
- This configuration is passed to Cowboy when starting listeners using cowboy:start_clear/3 or cowboy:start_tls/3 functions.</description>
+   Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, env =&amp;gt; cowboy_middleware:env(), inactivity_timeout =&amp;gt; timeout(), middlewares =&amp;gt; [module()], preface_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] } Configuration for the HTTP/2 protocol.
+ This configuration is passed to Cowboy when starting listeners using cowboy:start_clear/3 or cowboy:start_tls/3 functions.
+ It can be updated without restarting listeners using the Ranch functions ranch:get_protocol_options/1 and ranch:set_protocol_options/2.</description>
+    </item>
+    
+    <item>
+      <title>cowboy_http2(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_http2/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_http2/</guid>
+      <description>Name cowboy_http2 - HTTP/2
+   Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
+   Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, enable_connect_protocol =&amp;gt; boolean(), env =&amp;gt; cowboy_middleware:env(), inactivity_timeout =&amp;gt; timeout(), initial_connection_window_size =&amp;gt; 65535..16#7fffffff, initial_stream_window_size =&amp;gt; 0..16#7fffffff, max_concurrent_streams =&amp;gt; non_neg_integer() | infinity, max_decode_table_size =&amp;gt; non_neg_integer(), max_encode_table_size =&amp;gt; non_neg_integer(), max_frame_size_received =&amp;gt; 16384..16777215, max_frame_size_sent =&amp;gt; 16384..16777215 | infinity, middlewares =&amp;gt; [module()], preface_timeout =&amp;gt; timeout(), settings_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] } Configuration for the HTTP/2 protocol.</description>
     </item>
     
     <item>
@@ -3146,6 +3675,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_loop(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_loop/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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_middleware(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_middleware/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3198,6 +3740,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_middleware(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_middleware/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3258,6 +3813,21 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:binding(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.binding/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3302,6 +3872,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:binding(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.binding/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:bindings(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.bindings/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3350,6 +3931,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:bindings(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.bindings/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:body_length(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.body_length/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3398,6 +3991,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:body_length(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.body_length/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:cert(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.1/manual/cowboy_req.cert/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3434,6 +4039,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:cert(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.cert/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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;#8217;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}, {cert, &#34;path/to/cert.pem&#34;}, {verify, verify_peer} ], #{ env =&amp;gt; #{dispatch =&amp;gt; Dispatch} }).</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:delete_resp_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.delete_resp_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3482,6 +4099,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:delete_resp_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:has_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.has_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3530,6 +4159,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:has_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.has_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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).</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:has_resp_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.has_resp_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3582,6 +4223,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:has_resp_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:has_resp_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.has_resp_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3630,6 +4284,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:has_resp_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/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:header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3674,6 +4340,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:headers(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.headers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3726,6 +4403,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:headers(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.headers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:host(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.host/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3774,6 +4464,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:host(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.host/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:host_info(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.host_info/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3822,6 +4524,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:host_info(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.host_info/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.host_info/</guid>
+      <description>Name cowboy_req:host_info - Access the route&amp;#8217;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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:inform(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.1/manual/cowboy_req.inform/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3855,6 +4569,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:inform(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.inform/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:match_cookies(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.match_cookies/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3899,6 +4624,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:match_cookies(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.match_cookies/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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_qs(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.match_qs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3943,6 +4679,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:match_qs(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.match_qs/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:method(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.method/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -3991,6 +4738,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:method(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.method/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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;#8217;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;#8217;s HTTP method is returned as a binary string. While methods are case sensitive, standard methods are always uppercase.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:parse_cookies(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.parse_cookies/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4047,6 +4806,20 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:parse_cookies(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_cookies/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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([cookie], Req).
+ When the cookie header is missing, [] is returned.
+ While an empty cookie header is not valid, some clients do send it. Cowboy will in this case also return [].
+   Arguments  Req    The Req object.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:parse_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.parse_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4091,6 +4864,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:parse_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:parse_qs(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.parse_qs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4135,6 +4919,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:parse_qs(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_qs/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:path(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.path/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4187,6 +4982,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:path(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.path/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:path_info(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.path_info/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4235,6 +5043,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:path_info(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.path_info/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.path_info/</guid>
+      <description>Name cowboy_req:path_info - Access the route&amp;#8217;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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:peer(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.peer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4284,6 +5104,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:peer(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.peer/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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;#8217;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;#8217;s IP address and port number.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:port(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.port/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4336,6 +5168,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:port(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.port/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:push(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.push/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4380,6 +5225,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:push(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.push/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:qs(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.qs/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4428,6 +5284,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:qs(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.qs/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:read_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.read_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4472,6 +5340,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:read_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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_part(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.read_part/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4516,6 +5395,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:read_part(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_part/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.read_part_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4560,6 +5450,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:read_part_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/manual/cowboy_req.read_part_body/</guid>
+      <description>Name cowboy_req:read_part_body - Read the current part&amp;#8217;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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:read_urlencoded_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.read_urlencoded_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4608,6 +5509,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:read_urlencoded_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/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:reply(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.reply/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4652,6 +5565,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:reply(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.reply/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:resp_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.resp_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4700,6 +5624,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:resp_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.resp_header/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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_headers(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.resp_headers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4748,6 +5684,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:resp_headers(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.resp_headers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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).</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:scheme(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.scheme/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4800,6 +5748,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:scheme(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.scheme/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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;&#34;</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:set_resp_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.set_resp_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4848,6 +5809,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:set_resp_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/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_cookie(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.set_resp_cookie/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4896,6 +5869,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:set_resp_cookie(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:set_resp_header(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.set_resp_header/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4940,6 +5925,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:set_resp_header(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:set_resp_headers(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.set_resp_headers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -4988,6 +5984,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:set_resp_headers(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/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.4/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:sock(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.1/manual/cowboy_req.sock/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5024,6 +6032,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:sock(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.sock/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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;#8217;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;#8217;s local IP address and port number.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:stream_body(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.stream_body/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5072,6 +6092,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:stream_body(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_body/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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 :: iodata() 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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:stream_reply(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.stream_reply/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5120,6 +6152,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:stream_reply(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_reply/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_req:stream_trailers(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.stream_trailers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5144,6 +6188,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:stream_trailers(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_trailers/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:uri(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.uri/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5188,6 +6244,17 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:uri(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.uri/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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:version(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_req.version/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5236,6 +6303,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_req:version(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.version/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_rest(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_rest/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5288,6 +6367,19 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_rest(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_rest/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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_router(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_router/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5336,6 +6428,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_router(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_router/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.
+ When a route matches, the router sets the handler and handler_opts middleware environment values containing the handler module and initial state, respectively.</description>
+    </item>
+    
+    <item>
       <title>cowboy_router:compile(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_router.compile/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5384,6 +6488,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_router:compile(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_router.compile/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_static(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_static/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5432,6 +6548,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_static(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_static/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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 :: [Etag | Mimetypes] 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_stream(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_stream/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5480,6 +6608,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_stream(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_stream/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_stream/</guid>
+      <description>Name cowboy_handler - 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.</description>
+    </item>
+    
+    <item>
       <title>cowboy_websocket(3)</title>
       <link>https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_websocket/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
@@ -5528,6 +6668,18 @@ Crowdfund my salary or buy The Erlanger Playbook
     </item>
     
     <item>
+      <title>cowboy_websocket(3)</title>
+      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_websocket/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://ninenines.eu/docs/en/cowboy/2.4/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 :: {text | binary | ping | pong, binary()} OutFrame :: cow_ws:frame() %% see types below Info :: any() CallResult :: {ok, State} | {ok, State, hibernate} | {reply, OutFrame | [OutFrame], State} | {reply, OutFrame | [OutFrame], State, hibernate} | {stop, State} 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>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>
author	Loïc Hoguin <[email protected]>	2018-05-02 11:35:26 +0200
committer	Loïc Hoguin <[email protected]>	2018-05-02 11:35:26 +0200
commit	fec98300ec9af6c8b5f3120a60f217983c451076 (patch)
tree	9772977293124e8b9b5b253e44d8c2695cddfb44 /index.xml
parent	bfd2b6e01cbb36b0be0b3c860f5baf8d5b49fe7a (diff)
download	ninenines.eu-fec98300ec9af6c8b5f3120a60f217983c451076.tar.gz ninenines.eu-fec98300ec9af6c8b5f3120a60f217983c451076.tar.bz2 ninenines.eu-fec98300ec9af6c8b5f3120a60f217983c451076.zip