Statistics
| Branch: | Revision:

janus-gateway / conf / janus.transport.http.cfg.sample.in @ 1f44763c

History | View | Annotate | Download (3.38 KB)

1
; Web server stuff: whether any should be enabled, which ports they
2
; should use, whether security should be handled directly or demanded to
3
; an external application (e.g., web frontend) and what should be the
4
; base path for the Janus API protocol. You can also specify the
5
; threading model to use for the HTTP webserver: by default this is
6
; 'unlimited' (which means a thread per connection, as specified by the
7
; libmicrohttpd documentation), using a number will make use of a thread
8
; pool instead. Since long polls are involved, make sure you choose a
9
; value that doesn't keep new connections waiting.
10
[general]
11
json = indented				; Whether the JSON messages should be indented (default),
12
							; plain (no indentation) or compact (no indentation and no spaces)
13
base_path = /janus			; Base path to bind to in the web server (plain HTTP only)
14
threads = unlimited			; unlimited=thread per connection, number=thread pool
15
http = yes					; Whether to enable the plain HTTP interface
16
port = 8088					; Web server HTTP port
17
;interface = eth0			; Whether we should bind this server to a specific interface only
18
;ip = 192.168.0.1			; Whether we should bind this server to a specific IP address (v4 or v6) only
19
https = no					; Whether to enable HTTPS (default=no)
20
;secure_port = 8089			; Web server HTTPS port, if enabled
21
;secure_interface = eth0	; Whether we should bind this server to a specific interface only
22
;secure_ip = 192.168.0.1	; Whether we should bind this server to a specific IP address (v4 or v6) only
23
;acl = 127.,192.168.0.		; Only allow requests coming from this comma separated list of addresses
24

    
25
; Janus can also expose an admin/monitor endpoint, to allow you to check
26
; which sessions are up, which handles they're managing, their current
27
; status and so on. This provides a useful aid when debugging potential
28
; issues in Janus. The configuration is pretty much the same as the one
29
; already presented above for the webserver stuff, as the API is very
30
; similar: choose the base bath for the admin/monitor endpoint (/admin
31
; by default), ports, threading model, etc. Besides, you can specify
32
; a secret that must be provided in all requests as a crude form of
33
; authorization mechanism, and partial or full source IPs if you want to
34
; limit access basing on IP addresses. For security reasons, this
35
; endpoint is disabled by default, enable it by setting admin_http=yes.
36
[admin]
37
admin_base_path = /admin		; Base path to bind to in the admin/monitor web server (plain HTTP only)
38
admin_threads = unlimited		; unlimited=thread per connection, number=thread pool
39
admin_http = no					; Whether to enable the plain HTTP interface
40
admin_port = 7088				; Admin/monitor web server HTTP port
41
;admin_interface = eth0			; Whether we should bind this server to a specific interface only
42
;admin_ip = 192.168.0.1			; Whether we should bind this server to a specific IP address (v4 or v6) only
43
admin_https = no				; Whether to enable HTTPS (default=no)
44
;admin_secure_port = 7889		; Admin/monitor web server HTTPS port, if enabled
45
;admin_secure_interface = eth0	; Whether we should bind this server to a specific interface only
46
;admin_secure_ip = 192.168.0.1	; Whether we should bind this server to a specific IP address (v4 or v6) only
47
;admin_acl = 127.,192.168.0.	; Only allow requests coming from this comma separated list of addresses
48

    
49

    
50
; Certificate and key to use for HTTPS.
51
[certificates]
52
cert_pem = @certdir@/mycert.pem
53
cert_key = @certdir@/mycert.key