From 8459bebceb9533948193774371cbd9fd571b78ea Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Wed, 16 Oct 2019 09:48:31 +0200 Subject: Cowboy 2.7.0 --- docs/en/cowboy/2.6/manual/cowboy_req/index.html | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'docs/en/cowboy/2.6/manual/cowboy_req/index.html') diff --git a/docs/en/cowboy/2.6/manual/cowboy_req/index.html b/docs/en/cowboy/2.6/manual/cowboy_req/index.html index a1a7723a..dc824d75 100644 --- a/docs/en/cowboy/2.6/manual/cowboy_req/index.html +++ b/docs/en/cowboy/2.6/manual/cowboy_req/index.html @@ -193,7 +193,7 @@

Types

push_opts()

-
@@ -208,7 +208,7 @@ http://www.gnu.org/software/src-highlite -->

Push options.

By default, Cowboy will use the GET method, an empty query string, and take the scheme, host and port directly from the current request's URI.

read_body_opts()

-
@@ -221,7 +221,7 @@ http://www.gnu.org/software/src-highlite -->

Body reading options.

The defaults are function-specific.

req()

-
@@ -243,14 +243,14 @@ http://www.gnu.org/software/src-highlite -->

Contains information about the request and response. While some fields are publicly documented, others aren't and shouldn't be used.

You may add custom fields if required. Make sure to namespace them by prepending an underscore and the name of your application:

Setting a custom field
-
Req#{_myapp_auth_method => pubkey}.

resp_body()

-
@@ -265,7 +265,7 @@ http://www.gnu.org/software/src-highlite -->

It can take two forms: the actual data to be sent or a tuple indicating which file to send.

When sending data directly, the type is either a binary or an iolist. Iolists are an efficient way to build output. Instead of concatenating strings or binaries, you can simply build a list containing the fragments you want to send in the order they should be sent:

Example iolists usage
-
@@ -312,6 +312,8 @@ http://www.gnu.org/software/src-highlite --> +
  • 2.7
    • +
  • 2.6
  • 2.5
    • -- cgit v1.2.3