mirror of
https://github.com/asterisk/asterisk.git
synced 2026-04-28 01:32:57 +00:00
dbec5e0d8d
Persistent HTTP connection support is needed due to the increased usage of the Asterisk core HTTP transport and the frequency at which REST API calls are going to be issued. * Add http.conf session_keep_alive option to enable persistent connections. * Parse and discard optional chunked body extension information and trailing request headers. * Increased the maximum application/json and application/x-www-form-urlencoded body size allowed to 4k. The previous 1k was kind of small. * Removed a couple inlined versions of ast_http_manid_from_vars() by calling the function. manager.c:generic_http_callback() and res_http_post.c:http_post_callback() * Add missing va_end() in ast_ari_response_error(). * Eliminated unnecessary RAII_VAR() use in http.c:auth_create(). ASTERISK-23552 #close Reported by: Scott Griepentrog Review: https://reviewboard.asterisk.org/r/3691/ ........ Merged revisions 417880 from http://svn.asterisk.org/svn/asterisk/branches/12 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@417901 65c4cc65-6c06-0410-ace0-fbb531ad65f3
97 lines
3.4 KiB
Plaintext
97 lines
3.4 KiB
Plaintext
;
|
|
; Asterisk Builtin mini-HTTP server
|
|
;
|
|
;
|
|
; Note about Asterisk documentation:
|
|
; If Asterisk was installed from a tarball, then the HTML documentation should
|
|
; be installed in the static-http/docs directory which is
|
|
; (/var/lib/asterisk/static-http/docs) on linux by default. If the Asterisk
|
|
; HTTP server is enabled in this file by setting the "enabled", "bindaddr",
|
|
; and "bindport" options, then you should be able to view the documentation
|
|
; remotely by browsing to:
|
|
; http://<server_ip>:<bindport>/static/docs/index.html
|
|
;
|
|
[general]
|
|
;
|
|
; Whether HTTP/HTTPS interface is enabled or not. Default is no.
|
|
; This also affects manager/rawman/mxml access (see manager.conf)
|
|
;
|
|
;enabled=yes
|
|
;
|
|
; Address to bind to, both for HTTP and HTTPS. You MUST specify
|
|
; a bindaddr in order for the HTTP server to run. There is no
|
|
; default value.
|
|
;
|
|
bindaddr=127.0.0.1
|
|
;
|
|
; Port to bind to for HTTP sessions (default is 8088)
|
|
;
|
|
;bindport=8088
|
|
;
|
|
; Prefix allows you to specify a prefix for all requests
|
|
; to the server. The default is blank. If uncommented
|
|
; all requests must begin with /asterisk
|
|
;
|
|
;prefix=asterisk
|
|
;
|
|
; sessionlimit specifies the maximum number of httpsessions that will be
|
|
; allowed to exist at any given time. (default: 100)
|
|
;
|
|
;sessionlimit=100
|
|
;
|
|
; session_inactivity specifies the number of milliseconds to wait for
|
|
; more data over the HTTP connection before closing it.
|
|
;
|
|
; Default: 30000
|
|
;session_inactivity=30000
|
|
;
|
|
; session_keep_alive specifies the number of milliseconds to wait for
|
|
; the next HTTP request over a persistent connection.
|
|
;
|
|
; Set to 0 to disable persistent HTTP connections.
|
|
; Default: 15000
|
|
;session_keep_alive=15000
|
|
;
|
|
; Whether Asterisk should serve static content from static-http
|
|
; Default is no.
|
|
;
|
|
;enablestatic=yes
|
|
;
|
|
; Redirect one URI to another. This is how you would set a
|
|
; default page.
|
|
; Syntax: redirect=<from here> <to there>
|
|
; For example, if you are using the Asterisk-gui,
|
|
; it is convenient to enable the following redirect:
|
|
;
|
|
;redirect = / /static/config/index.html
|
|
;
|
|
; HTTPS support. In addition to enabled=yes, you need to
|
|
; explicitly enable tls, define the port to use,
|
|
; and have a certificate somewhere.
|
|
;tlsenable=yes ; enable tls - default no.
|
|
;tlsbindaddr=0.0.0.0:8089 ; address and port to bind to - default is bindaddr and port 8089.
|
|
;
|
|
;tlscertfile=</path/to/certificate.pem> ; path to the certificate file (*.pem) only.
|
|
;tlsprivatekey=</path/to/private.pem> ; path to private key file (*.pem) only.
|
|
; If no path is given for tlscertfile or tlsprivatekey, default is to look in current
|
|
; directory. If no tlsprivatekey is given, default is to search tlscertfile for private key.
|
|
;
|
|
; To produce a certificate you can e.g. use openssl. This places both the cert and
|
|
; private in same .pem file.
|
|
; openssl req -new -x509 -days 365 -nodes -out /tmp/foo.pem -keyout /tmp/foo.pem
|
|
;
|
|
; The post_mappings section maps URLs to real paths on the filesystem. If a
|
|
; POST is done from within an authenticated manager session to one of the
|
|
; configured POST mappings, then any files in the POST will be placed in the
|
|
; configured directory.
|
|
;
|
|
;[post_mappings]
|
|
;
|
|
; NOTE: You need a valid HTTP AMI mansession_id cookie with the manager
|
|
; config permission to POST files.
|
|
;
|
|
; In this example, if the prefix option is set to "asterisk", then using the
|
|
; POST URL: /asterisk/uploads will put files in /var/lib/asterisk/uploads/.
|
|
;uploads = /var/lib/asterisk/uploads/
|
|
;
|