| /dports/www/erlang-cowboy/cowboy-1.1.2/doc/src/guide/ |
| H A D | introduction.ezdoc | 3 Cowboy is a small, fast and modular HTTP server written in Erlang.
5 Cowboy aims to provide a complete HTTP stack, including its derivatives
6 SPDY, Websocket and REST. Cowboy currently supports HTTP/1.0, HTTP/1.1,
9 Cowboy is a high quality project. It has a small code base, is very
13 Cowboy is clean Erlang code. It includes hundreds of tests and its code
28 Cowboy is tested and supported on Linux.
30 Cowboy has been reported to work on other platforms, but we make no
35 Cowboy is developed for Erlang/OTP R16B01, R16B02, R16B03-1, 17.0 and
38 Cowboy may be compiled on other Erlang versions with small source code
43 Cowboy uses ^"Semantic Versioning 2.0.0^http://semver.org/^.
[all …]
|
| H A D | ws_protocol.ezdoc | 20 Websocket is an IETF standard. Cowboy supports the standard
27 Cowboy implements Websocket as a protocol upgrade. Once the
28 upgrade is performed from the `init/3` callback, Cowboy
33 The implementation of Websocket in Cowboy is validated using
35 covering all aspects of the protocol. Cowboy passes the
38 Cowboy's Websocket implementation also includes the
41 Cowboy will automatically use compression as long as the
|
| H A D | getting_started.ezdoc | 11 Cowboy, writing your first application and generating your first
13 you need to push your first Cowboy application to production.
55 will add Cowboy as a dependency and write a simple "Hello world!"
58 :: Cowboy setup
64 fetch and compile Cowboy. To do that we simply need to add one line
73 If you run `make run` now, Cowboy will be included in the release
74 and started automatically. This is not enough however, as Cowboy
75 doesn't do anything by default. We still need to tell Cowboy to
82 routes that Cowboy will use to map requests to handler modules.
83 Then we tell Cowboy to listen for connections.
[all …]
|
| H A D | http_req_life.ezdoc | 5 details of the Cowboy implementation.
19 Requests take the following route in Cowboy:
26 the light green is the Cowboy code that you can of
36 life of the request. If Cowboy can't parse the request,
50 so Cowboy will close the connection immediately after
73 Cowboy will include this header automatically in all
75 the closing of the socket if you want. When Cowboy sees
80 This snippet will force Cowboy to close the connection.
88 Cowboy will only accept a certain number of new requests
101 Cowboy implements the keep-alive mechanism by reusing
[all …]
|
| H A D | rest_flowcharts.ezdoc | 63 If the `options` callback is not defined, Cowboy will
80 When present, Cowboy will parse the headers and then
86 If a callback is not defined, Cowboy will select the
120 Cowboy prepares the response by first retrieving
171 for each of them. Cowboy will select the appropriate
178 it must return `false` and Cowboy will send an
185 Otherwise, return `true` to indicate success. Cowboy
212 Cowboy will then call the `delete_completed` callback.
216 `false`. Cowboy will assume `true` by default.
218 To finish, Cowboy checks if you set a response body,
[all …]
|
| H A D | req_body.ezdoc | 6 reading operations will only work once, as Cowboy will
9 Cowboy will not attempt to read the body until you do.
10 If handler execution ends without reading it, Cowboy
13 Cowboy provides different ways to read the request body.
57 By default, Cowboy will attempt to read up to a
73 If the body is larger than the limit, then Cowboy will return
81 Cowboy returns a `more` tuple when there is more body to
110 The `read_timeout` option defines the time Cowboy waits
115 Cowboy will by default decode the chunked transfer-encoding
151 By default Cowboy will reject bodies with a size above
|
| H A D | index.ezdoc | 1 ::: Cowboy User Guide
3 The Cowboy User Guide explores the modern Web and how to make
4 best use of Cowboy for writing powerful web applications.
6 :: Introducing Cowboy
|
| H A D | hooks.ezdoc | 3 Cowboy provides two hooks. `onrequest` is called once the request
9 The `onrequest` hook is called as soon as Cowboy finishes fetching
13 sent inside this hook, then Cowboy will move on to the next request,
17 and returns a request object. This function MUST NOT crash. Cowboy
52 Cowboy may or may not send a reply if this function crashes. If a reply
68 when it has not been provided before, and will let Cowboy proceed with
|
| H A D | resp.ezdoc | 10 and Cowboy will use them when you finally do reply.
15 Cowboy will make sure to send the mandatory headers with
23 that header names must be lowercase. Again, Cowboy will
32 You can override headers that Cowboy would send otherwise.
34 by Cowboy. For example, you can advertise yourself as a
46 Finally, you can also send a body with the response. Cowboy
103 override the default Cowboy headers.
111 and not the ones Cowboy will add when actually sending
166 without knowing the length in advance. Cowboy may be
181 read them. Cowboy will use the `sendfile` syscall when
|
| H A D | broken_clients.ezdoc | 9 Cowboy tries to follow the standard as much as possible,
11 Instead Cowboy focuses on the cases reported in the wild,
15 may fail to understand Cowboy's responses. There are of
20 Cowboy converts all headers it receives to lowercase, and
55 Req object response state to `waiting_stream`, Cowboy will
|
| H A D | ws_handlers.ezdoc | 31 Upon receiving this tuple, Cowboy will switch to the code
38 As long as the function returns an `ok` tuple, then Cowboy
47 handshake. When doing so, Cowboy will send a `400 Bad Request`
108 Cowboy will call `websocket_handle/3` whenever a text, binary,
110 case of ping and pong frames, no action is expected as Cowboy
128 Cowboy will call `websocket_info/3` whenever an Erlang message
146 Cowboy allows sending either a single frame or a list of
185 Cowboy will automatically respond to ping frames sent by the
189 Cowboy can be configured to automatically close the Websocket
209 following the return of the callback, Cowboy will hibernate
|
| H A D | multipart_req.ezdoc | 6 Cowboy defines two functions that allows you to get
42 too big, Cowboy will return what it read so far and
79 By default the body chunk Cowboy will return is limited
88 the part's body, Cowboy will automatically skip it when
106 Cowboy will automatically skip what remains.
115 entirely and Cowboy will automatically figure out what to do.
|
| H A D | middlewares.ezdoc | 3 Cowboy delegates the request processing to middleware components.
11 Cowboy will execute all middlewares in the given order, unless one
33 If an error happens during middleware processing, Cowboy will not try
51 set by any middleware. If set to anything other than `ok`, Cowboy
54 The middlewares that come with Cowboy may define or require other
|
| H A D | loop_handlers.ezdoc | 52 Once initialized, Cowboy will wait for messages to arrive
53 in the process' mailbox. When a message arrives, Cowboy
80 This will instruct Cowboy to end the request.
121 By default Cowboy will not attempt to close the connection
123 desirable, which is why you can set a timeout. Cowboy will
129 by another request, Cowboy is forced to buffer all data it
140 return. Just add the atom at the end and Cowboy will hibernate
|
| /dports/www/elixir-phoenix/phoenix-1.3.3/lib/phoenix/endpoint/ |
| H A D | cowboy_handler.ex | 3 The Cowboy adapter for Phoenix.
10 *NOTE*: This feature depends on the internals of Cowboy 1.0 API
12 without backwards compatibility, specifically when Cowboy 2.0 is released.
15 builtin Cowboy server with custom handlers. For example, to handle
33 {"/socket/long_poll", Plug.Adapters.Cowboy.Handler,
39 {:_, Plug.Adapters.Cowboy.Handler, {MyApp.Endpoint, []}}
48 {:_, Plug.Adapters.Cowboy.Handler, {MyApp.Endpoint, []}}
75 dispatches ++ [{:_, Plug.Adapters.Cowboy.Handler, {endpoint, []}}]
81 Plug.Adapters.Cowboy.child_spec(scheme, endpoint, [], config)
88 defp default_for(Phoenix.Transports.LongPoll), do: Plug.Adapters.Cowboy.Handler
[all …]
|
| /dports/net/rabbitmq/rabbitmq-server-3.9.11/deps/cowboy/ |
| H A D | README.asciidoc | 1 = Cowboy chapter
3 Cowboy is a small, fast and modern HTTP server for Erlang/OTP.
7 Cowboy aims to provide a *complete* HTTP stack in a *small* code base.
11 Cowboy provides *routing* capabilities, selectively dispatching requests
14 Because it uses Ranch for managing connections, Cowboy can easily be
17 Cowboy is *clean* and *well tested* Erlang code.
|
| /dports/textproc/elixir-earmark/earmark-1.2.5/test/regressions/ |
| H A D | i004_cowboy_readme_test.exs | 5 Cowboy
8 Cowboy is a small, fast and modular HTTP server written in Erlang.
13 Cowboy aims to provide a **complete** HTTP stack in a **small** code base.
17 Cowboy provides **routing** capabilities, selectively dispatching requests
20 Because it uses Ranch for managing connections, Cowboy can easily be
57 test "rendering the Cowboy webserver README" do
|
| /dports/devel/elixir-plug/plug-1.4.5/lib/plug/adapters/ |
| H A D | cowboy.ex | 1 defmodule Plug.Adapters.Cowboy do module
3 Adapter interface to the Cowboy webserver.
20 * `:dispatch` - manually configure Cowboy's dispatch.
28 * `:compress` - Cowboy will attempt to compress the response body.
62 Plug.Adapters.Cowboy.http MyPlug, [], port: 80
65 Plug.Adapters.Cowboy.shutdown MyPlug.HTTP
90 Plug.Adapters.Cowboy.https MyPlug, [],
99 Plug.Adapters.Cowboy.shutdown MyPlug.HTTPS
153 A function for starting a Cowboy server under Elixir v1.5 supervisors.
242 Cowboy returned 400 and there are no headers in the connection.
[all …]
|
| /dports/www/erlang-cowboy/cowboy-1.1.2/ |
| H A D | README.md | 1 Cowboy chapter
4 Cowboy is a small, fast and modular HTTP server written in Erlang.
9 Cowboy aims to provide a **complete** HTTP stack in a **small** code base.
13 Cowboy provides **routing** capabilities, selectively dispatching requests
16 Because it uses Ranch for managing connections, Cowboy can easily be
|
| /dports/www/erlang-cowboy/cowboy-1.1.2/doc/src/manual/ |
| H A D | index.ezdoc | 1 ::: Cowboy Function Reference
3 The function reference documents the public interface of Cowboy.
5 * ^"The Cowboy Application^cowboy_app
|
| H A D | http_status_codes.ezdoc | 3 This chapter aims to list all HTTP status codes that Cowboy
5 here only includes the replies that Cowboy sends, not user
11 Cowboy automatically sends a this status code before
60 Cowboy will send this status code for any of the
101 Cowboy will send this status code to the client if the
124 Cowboy will send this status code to the client if the
149 Cowboy only supports the versions 1.0 and 1.1 of HTTP.
|
| /dports/devel/elixir-plug/plug-1.4.5/test/plug/adapters/ |
| H A D | translator_test.exs | 19 {:ok, _pid} = Plug.Adapters.Cowboy.http __MODULE__, [], port: 9001
20 on_exit fn -> Plug.Adapters.Cowboy.shutdown(__MODULE__.HTTP) end
34 {:ok, _pid} = Plug.Adapters.Cowboy.http __MODULE__, [], port: 9002
35 on_exit fn -> Plug.Adapters.Cowboy.shutdown(__MODULE__.HTTP) end
|
| H A D | cowboy_test.exs | 4 import Plug.Adapters.Cowboy
11 {:_, [], Plug.Adapters.Cowboy.Handler, {Plug.Adapters.CowboyTest, [foo: :bar]}}
16 spec = {Plug.Adapters.Cowboy, [scheme: :http, plug: __MODULE__, options: [port: 4040]]}
87 Plug.Adapters.Cowboy.https MyPlug, [], []
91 Plug.Adapters.Cowboy.https MyPlug, [],
|
| /dports/www/erlang-cowboy/cowboy-1.1.2/examples/rest_hello_world/ |
| H A D | README.md | 29 server: Cowboy
52 server: Cowboy
67 server: Cowboy
82 server: Cowboy
|
| /dports/www/erlang-cowboy/cowboy-1.1.2/examples/rest_stream_response/ |
| H A D | README.md | 36 server: Cowboy
53 server: Cowboy
70 server: Cowboy
|