Merge remote-tracking branch 'origin/master'

doc/redirecting_a_url.rst

@@ -8,5 +8,5 @@ We can do them in Kapow! with little effort:
 In this example, we read the header ``User-Agent`` and feed it to the response:
 .. code-block:: bash
 
-   echo -n 302 | kapow set /response/status
+   kapow set /response/headers/Location 'http://example.org'
-   echo -n http://foobar-url.example | kapow set /response/headers/Location
+   kapow set /response/status 301

docs/source/theory/interfaces.rst

@@ -0,0 +1,33 @@
+Kapow! HTTP Interfaces
+======================
+
+`kapow server` sets up three HTTP server interfaces, each with a distinct and
+clear purpose.
+
+User Interface
+--------------
+
+The User HTTP interface is used to serve final user requests.
+
+By default it binds to address `0.0.0.0` and port `8080`, but can be changed via
+the ``--bind`` flag.
+
+
+Control Interface
+-----------------
+
+The Control HTTP interface is used by the command `kapow route` to
+administer the list of system routes.
+
+By default it binds to address `127.0.0.1` and port `8081`, but can be changed
+via the ``--control-bind`` flag.
+
+
+Data Interface
+--------------
+
+The Data HTTP interface is used by the commands `kapow get` and `kapow
+set` to exchange the data for a particular request.
+
+By default it binds to address `127.0.0.1` and port `8082`, but can be changed
+via the ``--data-bind`` flag.

docs/source/theory/request_life_cycle.rst

@@ -0,0 +1,29 @@
+Request Life Cycle
+==================
+
+This section describes the sequence of events happening for each request
+answered by the User HTTP Interface.
+
+#. The user makes a request to the User HTTP Interface
+
+#. The request is matched against the route table
+
+#. Kapow! provides a HANDLER_ID to identify this request
+
+#. Kapow! spawns the binary specified as entrypoint in the matching route
+
+   The default entrypoint is /bin/sh; we'll explain this workflow for now.
+
+   The spawned entrypoint is run with following variables added to its environment:
+- KAPOW_HANDLER_ID
+- KAPOW_DATAAPI_URL
+- KAPOW_CONTROLAPI_URL
+
+#.  During the lifetime of the shell, the request and response resources are available via these commands:
+
+- kapow get /request/...
+- kapow set /response/...
+
+TODO: link to resource tree
+
+#. When the shell dies, Kapow! finalizes the original request.

docs/source/theory/resource_tree.rst

@@ -0,0 +1,185 @@
+The Resource Tree
+=================
+
+This is the model that Kapow! uses to expose the internals of the user request
+being serviced.
+
+
+We use this tree to get access to any data that comes in the request,
+as well as to compose the response.
+
+We access the resource tree easily with the ``kapow set`` and ``kapow get``
+subcommands.
+
+
+Overview
+--------
+
+.. code-block:: plain
+
+    /                               The root of the resource paths tree
+    │
+    ├─ request                      All information related to the HTTP request.  Read-Only
+    │  ├──── method                 Used HTTP Method (GET, POST)
+    │  ├──── host                   Host part of the URL
+    │  ├──── path                   Complete URL path (URL-unquoted)
+    │  ├──── matches                Previously matched URL path parts
+    │  │     └──── <name>
+    │  ├──── params                 URL parameters (after the "?" symbol)
+    │  │     └──── <name>
+    │  ├──── headers                HTTP request headers
+    │  │     └──── <name>
+    │  ├──── cookies                HTTP request cookie
+    │  │     └──── <name>
+    │  ├──── form                   Form-urlencoded form fields (names only)
+    │  │     └──── <name>           Value of the form field with name <name>
+    │  ├──── files                  Files uploaded via multi-part form fields (names only)
+    │  │     └──── <name>
+    │  │           └──── filename   Original file name
+    │  │           └──── content    The file content
+    │  └──── body                   HTTP request body
+    │
+    └─ response                     All information related to the HTTP request.  Write-Only
+      ├──── status                 HTTP status code
+      ├──── headers                HTTP response headers
+      │     └──── <name>
+      ├──── cookies                HTTP request cookie
+      │     └──── <name>
+      ├──── body                   Response body.  Mutually exclusive with response/stream
+      └──── stream                 Alias for /response/body
+
+Resources
+---------
+
+``/request/method``
+~~~~~~~~~~~~~~~~~~~
+The HTTP method of the incoming request.
+
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get /request/method
+   GET
+
+``/request/host``
+~~~~~~~~~~~~~~~~~
+
+The ``Host`` header as defined in the HTTP/1.1 spec.
+
+Sample usage:
+
+If the user runs:
+
+.. code-block:: bash
+   $ curl http://kapow.example:8080
+
+
+then, when handling the request:
+
+.. code-block:: bash
+   $ kapow get /request/host
+   kapow.example
+
+
+``/request/path``
+~~~~~~~~~~~~~~~~~
+Contains the path substring of the URL.
+
+
+Sample usage:
+
+.. code-block:: bash
+   # GET http://url.example/foo/bar?q=1
+   $ kapow get /request/path
+   /foo/bar
+
+``/request/matches/<name>``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/request/params/<name>``
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/request/headers/<name>``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/request/cookies/<name>``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/request/form/<name>``
+~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/request/files/<name>``
+~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/request/files/<name>/filename``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/request/files/<name>/content``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/request/body``
+~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/response/status``
+~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/response/headers/<name>``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/response/cookies/<name>``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get
+
+``/response/body``
+~~~~~~~~~~~~~~~~~~
+Sample usage:
+
+.. code-block:: bash
+   $ kapow get