Here are the rest of the Liberator configuration items that define how Liberator handles HTTP connections with clients.
More HTTP-related configuration items can be found in HTTP Configuration (part 1).
add-authdir specifies an HTTP-authenticated directory.
add-authdir check-module [type] name [string] password [string array] realm [string] secure-passwords [boolean] username [string array] end-authdir
When check-module is TRUE, the Liberator's auth module is used to to authorise a user's access to the HTTP directory specified in name, instead of using the list of usernames and passwords supplied in this add-authdir item.
||string||/status||The full HTTP directory name.
The default is the Liberator's status page.
The passwords can be encrypted in MD5 hash format so that they are secure; in this case, set secure-passwords to
||string||Liberator Admin||The HTTP basic authentication realm. (This string is shown in the Liberator login window that pops up at the client when the login isn't through KeyMaster single sign-on.)|
||string array||admin||A space-separated list of usernames defining the users who can access the HTTP directory specified in name.
See Note 1 below.
add-authdir username Alf Bill Carl Dave password pwA pwB pwC pwD end-authdir
In the above example user
Alf's password is
Bill's password is
pwB, and so on.
add-authdir username Alf password pwA username Bill password pwB username Carl Dave password pwC pwD end-authdir
In the above example user
Alf's password is still
pwA, but it's been specified in a
password option that immediately follows the
username option for
Alf, and similarly for user
Bill whose password is
add-useragent enables various HTTP protocol extensions for a specific browser or browsers, as identified by the browser(s) user agent string.
add-useragent useragent-pattern [string] extensions flag1|flag2|flag3|... end-useragent
|useragent-pattern||string||[none]||A regular expression that Liberator uses to match the user agent string sent to it from a client’s browser.
There’s a useful list of the user agent strings sent by a wide variety of browsers at http://www.useragentstring.com/pages/useragentstring.php
You can also identify the user agent string sent to Liberator from a particular browser by logging into the Liberator from the browser and then looking in the Liberator’s http-access-log.
Flags that enable various HTTP protocol extensions. These flags allow you to turn on HTTP features that can improve utilisation of the client-Liberator connection for browsers whose user agent strings match the value of the useragent-pattern option.
Valid values are as for the http-extensions configuration item.
You can specify the flags in one extensions option, like this:
or in multiple options, like this:
http-extensions flag1 http-extensions flag2 http-extensions flag3
See the examples below.
add-useragent useragent-pattern MSIE extensions force-type5-chunked end-useragent
add-useragent useragent-pattern “MSIE 11\.” allow-extensions force-type5-chunked end-useragent
This example does the same as Example 1 above, but only applies to version 11 releases of the Microsoft Internet Explorer browser; that is, all browsers that return a user agent string containing the string "MSIE 11."
add-useragent useragent-pattern Chrome extensions allow-sse-deflate|allow-ws-permessage-deflate end-useragent
This example allows Liberator to negotiate with the Chrome browser to use compression for the HTML5 Server-Sent Events connection type and to use DEFLATE compression of Websocket frames.