diff options
| author | David M. Lee <dlee@digium.com> | 2013-11-27 15:48:39 +0000 |
|---|---|---|
| committer | David M. Lee <dlee@digium.com> | 2013-11-27 15:48:39 +0000 |
| commit | fccb427c88e6b6e0ae8627ffcdc06f4ae5077d34 (patch) | |
| tree | f3aa4bd4148bd818be174ee8648c3d50300ceec7 /res/res_ari.c | |
| parent | fd33969240111a9ad2fdd305461265b315ce13dd (diff) | |
ari:Add application/json parameter support
The patch allows ARI to parse request parameters from an incoming JSON
request body, instead of requiring the request to come in as query
parameters (which is just weird for POST and DELETE) or form
parameters (which is okay, but a bit asymmetric given that all of our
responses are JSON).
For any operation that does _not_ have a parameter defined of type
body (i.e. "paramType": "body" in the API declaration), if a request
provides a request body with a Content type of "application/json", the
provided JSON document is parsed and searched for parameters.
The expected fields in the provided JSON document should match the
query parameters defined for the operation. If the parameter has
'allowMultiple' set, then the field in the JSON document may
optionally be an array of values.
(closes issue ASTERISK-22685)
Review: https://reviewboard.asterisk.org/r/2994/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@403177 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'res/res_ari.c')
| -rw-r--r-- | res/res_ari.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/res/res_ari.c b/res/res_ari.c index 4ceb3847e..108f6c7e1 100644 --- a/res/res_ari.c +++ b/res/res_ari.c @@ -539,7 +539,7 @@ void ast_ari_invoke(struct ast_tcptls_session_instance *ser, return; } - callback(get_params, path_vars, headers, response); + callback(ser, get_params, path_vars, headers, response); if (response->message == NULL && response->response_code == 0) { /* Really should not happen */ ast_log(LOG_ERROR, "ARI %s %s not implemented\n", |