summaryrefslogtreecommitdiffstats
path: root/articles/cowboy-2.2.0/index.html
diff options
context:
space:
mode:
authorLoïc Hoguin <[email protected]>2018-06-13 09:54:12 +0200
committerLoïc Hoguin <[email protected]>2018-06-13 09:54:12 +0200
commit92b54aacc0de5446dd5497c39897b0bbff72e626 (patch)
treec3a98cfec636d1271f5804e5c19b35b208bba00d /articles/cowboy-2.2.0/index.html
parent8b5c3dc972b99f174750123c9e4abc96259c34a9 (diff)
downloadninenines.eu-92b54aacc0de5446dd5497c39897b0bbff72e626.tar.gz
ninenines.eu-92b54aacc0de5446dd5497c39897b0bbff72e626.tar.bz2
ninenines.eu-92b54aacc0de5446dd5497c39897b0bbff72e626.zip
Rebuild using Asciideck
Diffstat (limited to 'articles/cowboy-2.2.0/index.html')
-rw-r--r--articles/cowboy-2.2.0/index.html51
1 files changed, 11 insertions, 40 deletions
diff --git a/articles/cowboy-2.2.0/index.html b/articles/cowboy-2.2.0/index.html
index 06608ccc..8272096d 100644
--- a/articles/cowboy-2.2.0/index.html
+++ b/articles/cowboy-2.2.0/index.html
@@ -69,49 +69,20 @@
</p>
</header>
-<div class="paragraph"><p>Cowboy <code>2.2.0</code> has been released!</p></div>
-<div class="paragraph"><p>This release focused on adding features required for writing
-gRPC servers and on completing test suites for the core
-HTTP RFCs.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-The <code>cowboy_req:stream_trailers/2</code> function has been
- added. It terminates the streamed response by adding
- some trailer field values. This feature is required
- for gRPC.
-</p>
+<p>Cowboy <code>2.2.0</code> has been released!</p>
+<p>This release focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs.</p>
+<ul><li>The <code>cowboy_req:stream_trailers/2</code> function has been added. It terminates the streamed response by adding some trailer field values. This feature is required for gRPC.
</li>
-<li>
-<p>
-The <code>max_skip_body_length</code> option was added. It controls
- how much of the request body we are willing to skip
- to get to the next request for HTTP/1.1 keep-alive
- connections.
-</p>
+<li>The <code>max_skip_body_length</code> option was added. It controls how much of the request body we are willing to skip to get to the next request for HTTP/1.1 keep-alive connections.
</li>
-<li>
-<p>
-The CONNECT and TRACE methods have been disabled
- entirely. They are currently not implemented and
- their behavior is very specific (unlike most other
- methods) so it is safer to prevent their use.
-</p>
+<li>The CONNECT and TRACE methods have been disabled entirely. They are currently not implemented and their behavior is very specific (unlike most other methods) so it is safer to prevent their use.
</li>
-</ul></div>
-<div class="paragraph"><p>Many bugs have also been fixed. A more complete
-list of changes can be found in the migration guide:
-<a href="https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_2.1/">Migrating from Cowboy 2.1 to 2.2</a>.</p></div>
-<div class="paragraph"><p>The next two releases will tentatively focus on improving
-the support for cookies and CORS, but I&#8217;m open to suggestions.
-If there is a pain point in Cowboy 2.2 I would love to hear
-about it.</p></div>
-<div class="paragraph"><p>You can donate to this project via
-<a href="https://salt.bountysource.com/teams/ninenines">BountySource</a>
-because I need to eat snacks when I write code.
-Thanks in advance!</p></div>
-<div class="paragraph"><p>As usual, any feedback is appreciated, and any issues
-should be reported by opening a ticket. Thanks!</p></div>
+</ul>
+<p>Many bugs have also been fixed. A more complete list of changes can be found in the migration guide: <a href="https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_2.1/">Migrating from Cowboy 2.1 to 2.2</a>.</p>
+<p>The next two releases will tentatively focus on improving the support for cookies and CORS, but I&apos;m open to suggestions. If there is a pain point in Cowboy 2.2 I would love to hear about it.</p>
+<p>You can donate to this project via <a href="https://salt.bountysource.com/teams/ninenines">BountySource</a> because I need to eat snacks when I write code. Thanks in advance!</p>
+<p>As usual, any feedback is appreciated, and any issues should be reported by opening a ticket. Thanks!</p>
+
</article>
</div>