config: fix typo, 'apisecret' -> 'api_secret'

speak · Sep 2, 2015 · be568a2 · be568a2
1 parent 0afecf3
commit be568a2
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/conf/janus.cfg.sample.in b/conf/janus.cfg.sample.in
@@ -8,7 +8,7 @@ plugins_folder = @plugindir@		; Plugins folder
 debug_level = 4				; Debug/logging level, valid values are 0-7
 ;debug_timestamps = yes		; Whether to show a timestamp for each log line
 ;debug_colors = no			; Whether colors should be disabled in the log
-;apisecret = janusrocks		; String that all Janus requests must contain
+;api_secret = janusrocks		; String that all Janus requests must contain
 ;							to be accepted/authorized by the Janus core.
 ;							Useful if you're wrapping all Janus API requests
 ;							in your servers (that is, not in the browser,

diff --git a/mainpage.dox b/mainpage.dox
@@ -1103,7 +1103,7 @@ GET http://host:port/janus/<sessionid>?maxev=5
  * 
  * Configuring the API secret mechanism is easy enough: you can do that
  * either via the command line (\c -a or \c --apisecret ) or in the
- * \c janus.cfg configuration (\c apisecret value in the \c general section).
+ * \c janus.cfg configuration (\c api_secret value in the \c general section).
  * When enabled, all requests addressed to that Janus instance \b MUST
  * also contain an \c apisecret field in the Janus message headers. For
  * instance, this message presented above would fail: