diff options
| author | David M. Lee <dlee@digium.com> | 2013-04-22 14:58:53 +0000 |
|---|---|---|
| committer | David M. Lee <dlee@digium.com> | 2013-04-22 14:58:53 +0000 |
| commit | 1c21b8575bfd70b98b1102fd3dd09fc0bc335e14 (patch) | |
| tree | 9a6ef6074e545ad2768bc1994e1a233fc1443729 /configs/stasis_http.conf.sample | |
| parent | 1871017cc6bd2e2ce7c638eeb6813e982377a521 (diff) | |
This patch adds a RESTful HTTP interface to Asterisk.
The API itself is documented using Swagger, a lightweight mechanism for
documenting RESTful API's using JSON. This allows us to use swagger-ui
to provide executable documentation for the API, generate client
bindings in different languages, and generate a lot of the boilerplate
code for implementing the RESTful bindings. The API docs live in the
rest-api/ directory.
The RESTful bindings are generated from the Swagger API docs using a set
of Mustache templates. The code generator is written in Python, and
uses Pystache. Pystache has no dependencies, and be installed easily
using pip. Code generation code lives in rest-api-templates/.
The generated code reduces a lot of boilerplate when it comes to
handling HTTP requests. It also helps us have greater consistency in the
REST API.
(closes issue ASTERISK-20891)
Review: https://reviewboard.asterisk.org/r/2376/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@386232 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'configs/stasis_http.conf.sample')
| -rw-r--r-- | configs/stasis_http.conf.sample | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/configs/stasis_http.conf.sample b/configs/stasis_http.conf.sample new file mode 100644 index 000000000..1527a32be --- /dev/null +++ b/configs/stasis_http.conf.sample @@ -0,0 +1,25 @@ +[general] +enabled = yes ; When set to no, stasis-http support is disabled +;pretty = no ; When set to yes, responses from stasis-http are +; ; formatted to be human readable +;allowed_origins = ; Comma separated list of allowed origins, for +; ; Cross-Origin Resource Sharing. May be set to * to allow +; ; all origins. + +;[user-username] +;read_only = no ; When set to yes, user is only authorized for +; ; read-only requests +; +; If a password is specified, user must authenticate using HTTP Basic +; authentication. If no password is specified, then the user may authenticate +; simply by adding ?api_key=username to their requests. +; +;password = ; Crypted or plaintext password (see crypt_password) +; +; crypt_password may be set to crypt (the default) or plain. When set to crypt, +; crypt(3) is used to encrypt the password. A crypted password can be generated +; using mkpasswd -m sha-512. +; +; When set to plain, the password is in plaintext +; +;crypt_password = plain |