Roxen.git/ server/ translations/ eng/ roxen_config.xml > e3aab75e2ac4274dba06769e1caf41b5c67c0546 [Annotate]

<?xml version="1.0" encoding="iso-8859-1"?> 

<locale version="1.0"/> 

<project>roxen_config</project> 

<language>English</language> 

<dumped>964529600</dumped> 

<file>../base_server/roxen.pike</file> 

<file>../base_server/configuration.pike</file> 

<file>../base_server/global_variables.pike</file> 

<file>../modules/configuration/config_tags.pike</file> 

<file>../modules/configuration/config_userdb.pike</file> 

<file>../modules/configuration/config_filesystem.pike</file> 

<file>../config_interface/standard/template</file> 

<file>../config_interface/standard/settings.html</file> 

<file>../config_interface/standard/logutil.pike</file> 

<file>../config_interface/standard/topmenu.pike</file> 

<file>../config_interface/standard/cv_startpage_tabs.pike</file> 

<file>../config_interface/standard/users.html</file> 

<file>../config_interface/standard/user_form.pike</file> 

<file>../config_interface/standard/user_delete.pike</file> 

<file>../config_interface/standard/actions/index.html</file> 

<file>../config_interface/standard/actions/tablist.pike</file> 

<file>../config_interface/standard/actions/flush.pike</file> 

<file>../config_interface/standard/actions/restart.pike</file> 

<file>../config_interface/standard/actions/listfonts.pike</file> 

<file>../config_interface/standard/actions/feature_list.pike</file> 

<file>../config_interface/standard/event_log/index.html</file> 

<file>../config_interface/standard/event_log/log.pike</file> 

<file>../config_interface/standard/sites/index.html</file> 

<file>../config_interface/standard/sites/log.pike</file> 

<file>../config_interface/standard/sites/site_content.pike</file> 

<file>../config_interface/standard/sites/site_header.pike</file> 

<file>../config_interface/standard/sites/new_site.html</file> 

<file>../config_interface/standard/sites/create_site.pike</file> 

<file>../config_interface/standard/sites/drop_site.pike</file> 

<file>../config_interface/standard/sites/drop_site.html</file> 

<file>../config_interface/standard/sites/add_module.pike</file> 

<file>../config_interface/standard/sites/config_left_item.pike</file> 

<file>../config_interface/standard/sites/site_templates/common.pike</file> 

<added id="1"/> 

<!-- [1] "No virtual servers enabled" --> 

<t id="1"></t> 

<!-- [2] "Sent data" --> 

<t id="2"></t> 

<!-- [3] "sec" --> 

<t id="3"></t> 

<!-- [4] "Sent headers" --> 

<t id="4"></t> 

<!-- [5] "Number of requests" --> 

<t id="5"></t> 

<!-- [6] "min" --> 

<t id="6"></t> 

<!-- [7] "Received data" --> 

<t id="7"></t> 

<!-- [8] "FTP users (total)" --> 

<t id="8"></t> 

<!-- [9] "FTP users (now)" --> 

<t id="9"></t> 

<!-- [10] "FTP statistics" --> 

<t id="10"></t> 

<!-- [11] "Reloaded %s. 

" --> 

<t id="11"></t> 

<!-- [12] "Priority" --> 

<t id="12"></t> 

<!-- [13] "The priority of the module. 9 is highest and 0 is lowest. Modules with the same priority can be assumed to be called in random order" --> 

<t id="13"></t> 

<!-- [14] "Security: Realm" --> 

<t id="14"></t> 

<!-- [15] "The realm to use when requesting password from the client. Usually used as an informative message to the user." --> 

<t id="15"></t> 

<!-- [16] "Security: Patterns" --> 

<t id="16"></t> 

<!-- [17] "This is the 'security level=value' list.&lt;br /&gt;Each security level can be any or more from this list:&lt;hr noshade="noshade" /&gt;allow ip=&lt;i&gt;IP&lt;/i&gt;/&lt;i&gt;bits&lt;/i&gt;&lt;br /&gt;allow ip=&lt;i&gt;IP&lt;/i&gt;:&lt;i&gt;mask&lt;/i&gt;&lt;br /&gt;allow ip=&lt;i&gt;pattern&lt;/i&gt;&lt;br /&gt;allow user=&lt;i&gt;username&lt;/i&gt;,...&lt;br /&gt;deny ip=&lt;i&gt;IP&lt;/i&gt;/&lt;i&gt;bits&lt;/i&gt;&lt;br /&gt;deny ip=&lt;i&gt;IP&lt;/i&gt;:&lt;i&gt;mask&lt;/i&gt;&lt;br /&gt;deny ip=&lt;i&gt;pattern&lt;/i&gt;&lt;br /&gt;&lt;hr noshade="noshade" /&gt;In patterns: * matches one or more characters, and ? matches one character.&lt;p&gt;In username: 'any' stands for any valid account (from .htaccess or an auth module. The default (used when _no_ entries are present) is 'allow ip=*', allowing everyone to access the module.&lt;/p&gt;" --> 

<t id="17"></t> 

<!-- [18] "Security: Security level" --> 

<t id="18"></t> 

<!-- [19] "The modules security level is used to determine if a  request should be handled by the module. 

<p><h2>Security level vs Trust level</h2> Each module has a configurable <i>security level</i>. Each request has an assigned trust level. Higher <i>trust levels</i> grants access to modules with higher <i>security levels</i>. 

<p><h2>Definitions</h2><ul> <li>A requests initial Trust level is infinitely high.</li> <li> A request will only be handled by a module if its     <i>trust level</i> is higher or equal to the     <i>security level</i> of the module.</li> <li> Each time the request is handled by a module the     <i>trust level</i> of the module will be set to the      lower of its <i>trust level</i> and the modules     <i>security level</i>.</li> </ul></p> 

<p><h2>Example</h2> Modules:<ul> <li>  User filesystem, <i>security level</i> 1</li> <li>  Filesystem module, <i>security level</i> 3</li> <li>  CGI module, <i>security level</i> 2</li> </ul></p> 

<p>A request handled by "User filesystem" is assigned a <i>trust level</i> of one after the <i>security level</i> of that module. That request can then not be handled by the "CGI module" since that module has a higher <i>security level</i> than the requests trust level.</p> 

<p>On the other hand, a request handled by the the "Filsystem module" could later be handled by the "CGI module".</p>" --> 

<t id="19"></t> 

<!-- [20] "Default site" --> 

<t id="20"></t> 

<!-- [21] "If true, this site will be selected in preference of other sites when virtual hosting is used and no host header is supplied, or the supplied host header does not match the address of any of the other servers." --> 

<t id="21"></t> 

<!-- [22] "Virtual server comment" --> 

<t id="22"></t> 

<!-- [23] "This text will be visible in the administration interface, it can be quite useful to use as a memory helper." --> 

<t id="23"></t> 

<!-- [24] "Virtual server name" --> 

<t id="24"></t> 

<!-- [25] "This is the name that will be used in the configuration interface. If this is left empty, the actual name of the virtual server will be used." --> 

<t id="25"></t> 

<!-- [26] "Logging: Format" --> 

<t id="26"></t> 

<!-- [27] "What format to use for logging. The syntax is: 

<pre>response-code or *: Log format for that response code 

Log format is normal characters, or one or more of the variables below: 

\n \t \r       -- As in C, newline, tab and linefeed 

$char(int)     -- Insert the (1 byte) character specified by the integer. 

$wchar(int)    -- Insert the (2 byte) word specified by the integer. 

$int(int)      -- Insert the (4 byte) word specified by the integer. 

$^             -- Supress newline at the end of the logentry 

$host          -- The remote host name, or ip number. 

$ip_number     -- The remote ip number. 

$bin-ip_number -- The remote host id as a binary integer number. 

$cern_date     -- Cern Common Log file format date. 

$bin-date      -- Time, but as an 32 bit integer in network byteorder 

$method        -- Request method 

$resource      -- Resource identifier 

$full_resource -- Full requested resource, including any query fields 

$protocol      -- The protocol used (normally HTTP/1.0) 

$response      -- The response code sent 

$bin-response  -- The response code sent as a binary short number 

$length        -- The length of the data section of the reply 

$bin-length    -- Same, but as an 32 bit integer in network byteorder 

$request-time  -- The time the request took (seconds) 

$referer       -- the header 'referer' from the request, or '-'. 

$user_agent    -- the header 'User-Agent' from the request, or '-'. 

$user          -- the name of the auth user used, if any 

$user_id       -- A unique user ID, if cookies are supported, 

                  by the client, otherwise '0' 

</pre>" --> 

<t id="27"></t> 

<!-- [28] "Logging: Enabled" --> 

<t id="28"></t> 

<!-- [29] "Log requests" --> 

<t id="29"></t> 

<!-- [30] "Logging: Log file" --> 

<t id="30"></t> 

<!-- [31] "The log file. &lt;pre&gt;%y    Year  (e.g. '1997') 

%m    Month (e.g. '08') 

%d    Date  (e.g. '10' for the tenth) 

%h    Hour  (e.g. '00') 

%H    Hostname 

</pre>" --> 

<t id="31"></t> 

<!-- [32] "Logging: No Logging for" --> 

<t id="32"></t> 

<!-- [33] "Don't log requests from hosts with an IP number which matches any of the patterns in this list. This also affects the access counter log." --> 

<t id="33"></t> 

<!-- [34] "Domain" --> 

<t id="34"></t> 

<!-- [35] "The domainname of the server. The domainname is used to generate default URLs, and to generate email addresses." --> 

<t id="35"></t> 

<!-- [36] "Primary Server URL" --> 

<t id="36"></t> 

<!-- [37] "This is the main server URL, where your start page is located. Please note that you also have to configure the 'URLs' variable." --> 

<t id="37"></t> 

<!-- [38] "URLs" --> 

<t id="38"></t> 

<!-- [39] "Bind to these URLs. You can use '*' and '?' to perform globbing (using any of these will default to binding to all IP-numbers on your machine).  The possible protocols are http, fhttp (a faster version of the normal HTTP protocol, but not 100% compatible with all modules) https, ftp, ftps, gopher and tetris." --> 

<t id="39"></t> 

<!-- [40] "Internal module resource mountpoint" --> 

<t id="40"></t> 

<!-- [41] "Some modules may want to create links to internal resources. This setting configures an internally handled location that can be used for such purposes.  Simply select a location that you are not likely to use for regular resources." --> 

<t id="41"></t> 

<!-- [42] "Bandwidth Throttling: Server: Enabled" --> 

<t id="42"></t> 

<!-- [43] "If set, per-server bandwidth throttling will be enabled. It will allow you to limit the total available bandwidth for this Virtual Server.&lt;br /&gt;Bandwidth is assigned using a Token Bucket. The principle under which it works is: for each byte we send we use a token. Tokens are added to a repository at a constant rate. When there's not enough, we can't transmit. When there's too many, they "spill" and are lost." --> 

<t id="43"></t> 

<!-- [44] "Bandwidth Throttling: Server: Average available bandwidth" --> 

<t id="44"></t> 

<!-- [45] "This is the average bandwidth available to this Virtual Server in bytes/sec (the bucket "fill rate")." --> 

<t id="45"></t> 

<!-- [46] "Bandwidth Throttling: Server: Bucket Depth" --> 

<t id="46"></t> 

<!-- [47] "This is the maximum depth of the bucket. After a long enough period of inactivity, a request will get this many unthrottled bytes of data, before throttling kicks back in.&lt;br&gt;Set equal to the Fill Rate in order not to allow any data bursts. This value determines the length of the time over which the bandwidth is averaged." --> 

<t id="47"></t> 

<!-- [48] "Bandwidth Throttling: Server: Minimum Grant" --> 

<t id="48"></t> 

<!-- [49] "When the bandwidth availability is below this value, connections will be delayed rather than granted minimal amounts of bandwidth. The purpose is to avoid sending too small packets (which would increase the IP overhead)." --> 

<t id="49"></t> 

<!-- [50] "Bandwidth Throttling: Server: Maximum Grant" --> 

<t id="50"></t> 

<!-- [51] "This is the maximum number of bytes assigned in a single request to a connection. Keeping this number low will share bandwidth more evenly among the pending connections, but keeping it too low will increase IP overhead and (marginally) CPU usage. You'll want to set it just a tiny bit lower than any integer multiple of your network's MTU (typically 1500 for ethernet)." --> 

<t id="51"></t> 

<!-- [52] "Bandwidth Throttling: Request: Enabled" --> 

<t id="52"></t> 

<!-- [53] "If set, per-request bandwidth throttling will be enabled." --> 

<t id="53"></t> 

<!-- [54] "Bandwidth Throttling: Request: Minimum guarranteed bandwidth" --> 

<t id="54"></t> 

<!-- [55] "The maximum bandwidth each connection (in bytes/sec) can use is determined combining a number of modules. But doing so can lead to too small or even negative bandwidths for particularly unlucky requests. This variable guarantees a minimum bandwidth for each request." --> 

<t id="55"></t> 

<!-- [56] "Bandwidth Throttling: Request: Bucket Depth Multiplier" --> 

<t id="56"></t> 

<!-- [57] "The average bandwidth available for each request will be determined by the modules combination. The bucket depth will be determined multiplying the rate by this factor." --> 

<t id="57"></t> 

<!-- [58] "Messages: No such file" --> 

<t id="58"></t> 

<!-- [59] "What to return when there is no resource or file available at a certain location." --> 

<t id="59"></t> 

<!-- [60] "Welcome text" --> 

<t id="60"></t> 

<!-- [61] "The text shown to the user on connect" --> 

<t id="61"></t> 

<!-- [62] "User session limit" --> 

<t id="62"></t> 

<!-- [63] "The maximum number of times a user can connect at once. 0 means unlimited." --> 

<t id="63"></t> 

<!-- [64] "Allow named ftp" --> 

<t id="64"></t> 

<!-- [65] "If yes, non-anonymous users can connect" --> 

<t id="65"></t> 

<!-- [66] "Allow login with incorrect password/user" --> 

<t id="66"></t> 

<!-- [67] "If yes, users can connect with the wrong password and/or username. This is useful since things like .htaccess files can later on authenticate the user." --> 

<t id="67"></t> 

<!-- [68] "Allow anonymous ftp" --> 

<t id="68"></t> 

<!-- [69] "If yes, anonymous users is allowed to connect." --> 

<t id="69"></t> 

<!-- [70] "Shell database" --> 

<t id="70"></t> 

<!-- [71] "If this string is set to anything but the empty string, it should point to a file containing a list of valid shells. Users with shells that does not figure in this list will not be allowed to log in." --> 

<t id="71"></t> 

<!-- [72] "Show internal errors" --> 

<t id="72"></t> 

<!-- [73] "Show 'Internal server error' messages to the user. This is very useful if you are debugging your own modules or writing Pike scripts." --> 

<t id="73"></t> 

<!-- [74] "Logging: Set unique user id cookies" --> 

<t id="74"></t> 

<!-- [75] "If set to Yes, all users of your server whose clients support cookies will get a unique 'user-id-cookie', this can then be used in the log and in scripts to track individual users." --> 

<t id="75"></t> 

<!-- [76] "Logging: Set ID cookies only once" --> 

<t id="76"></t> 

<!-- [77] "If set to Yes, Roxen will attempt to set unique user ID cookies only upon receiving the first request (and again after some minutes). Thus, if the user doesn't allow the cookie to be set, she won't be bothered with multiple requests." --> 

<t id="77"></t> 

<!-- [78] "Logging method" --> 

<t id="78"></t> 

<!-- [79] "None - No log&lt;br /&gt;CommonLog - A common log in a file&lt;br /&gt;Compat - Log through Roxen's normal logging format.&lt;br /&gt;&lt;p&gt;Please note that compat limits Roxen to less than 1k requests/second.&lt;/p&gt;" --> 

<t id="79"></t> 

<!-- [80] "Log file" --> 

<t id="80"></t> 

<!-- [81] "This file is used if logging is done using the CommonLog method." --> 

<t id="81"></t> 

<!-- [82] "Ram cache" --> 

<t id="82"></t> 

<!-- [83] "The size of the ram cache, in MegaBytes" --> 

<t id="83"></t> 

<!-- [84] "Client timeout" --> 

<t id="84"></t> 

<!-- [85] "The maximum time Roxen will wait for a client before giving up, and close the connection, in seconds" --> 

<t id="85"></t> 

<!-- [86] "SSL certificate file" --> 

<t id="86"></t> 

<!-- [87] "The SSL certificate file to use. The path is relative to %s" --> 

<t id="87"></t> 

<!-- [88] "SSL key file" --> 

<t id="88"></t> 

<!-- [89] "The SSL key file to use. The path is relative to %s, you do not have to specify a key file, leave this field empty to use the certificate file only" --> 

<t id="89"></t> 

<!-- [90] "Logging: Log entire file length in restored connections" --> 

<t id="90"></t> 

<!-- [91] "If this toggle is enabled log entries for restored connections will log the amount of sent data plus the restoration location. Ie if a user has downloaded 100 bytes of a file already, and makes a Range request fetching the remaining 900 bytes, the log entry will log it as if the entire 1000 bytes were downloaded. &lt;p&gt;This is useful if you want to know if downloads were successful (the user has the complete file downloaded). The drawback is that bandwidth statistics on the log file will be incorrect. The statistics in Roxen will continue being correct." --> 

<t id="91"></t> 

<!-- [92] "Default font" --> 

<t id="92"></t> 

<!-- [93] "The default font to use when modules request a font." --> 

<t id="93"></t> 

<!-- [94] "Font directories" --> 

<t id="94"></t> 

<!-- [95] "This is where the fonts are located." --> 

<t id="95"></t> 

<!-- [96] "Logging: Log directory prefix" --> 

<t id="96"></t> 

<!-- [97] "This is the default file path that will be prepended to the log file path in all the default modules and the virtual server." --> 

<t id="97"></t> 

<!-- [98] "Cache: Proxy Disk Cache Enabled" --> 

<t id="98"></t> 

<!-- [99] "If set to Yes, caching will be enabled." --> 

<t id="99"></t> 

<!-- [100] "Cache: Proxy Disk Cache Clean size" --> 

<t id="100"></t> 

<!-- [101] "Minimum number of Megabytes removed when a garbage collect is done." --> 

<t id="101"></t> 

<!-- [102] "Cache: Proxy Disk Cache Minimum available free space and inodes (in %)" --> 

<t id="102"></t> 

<!-- [103] "If less than this amount of disk space or inodes (in %) is left, the cache will remove a few files. This check may work half-hearted if the diskcache is spread over several filesystems." --> 

<t id="103"></t> 

<!-- [104] "Cache: Proxy Disk Cache Size" --> 

<t id="104"></t> 

<!-- [105] "How many MB may the cache grow to before a garbage collect is done?" --> 

<t id="105"></t> 

<!-- [106] "Cache: Proxy Disk Cache Maximum number of files" --> 

<t id="106"></t> 

<!-- [107] "How many cache files (inodes) may be on disk before a garbage collect is done ? May be left zero to disable this check." --> 

<t id="107"></t> 

<!-- [108] "Cache: Proxy Disk Cache bytes per second" --> 

<t id="108"></t> 

<!-- [109] "How file size should be treated during garbage collect. Each X bytes counts as a second, so that larger files will be removed first." --> 

<t id="109"></t> 

<!-- [110] "Cache: Proxy Disk Cache Base Cache Dir" --> 

<t id="110"></t> 

<!-- [111] "This is the base directory where cached files will reside. To avoid mishaps, 'roxen_cache/' is always prepended to this variable." --> 

<t id="111"></t> 

<!-- [112] "Cache: Proxy Disk Cache Number of hash directories" --> 

<t id="112"></t> 

<!-- [113] "This is the number of directories to hash the contents of the disk cache into.  Changing this value currently invalidates the whole cache, since the cache cannot find the old files.  In the future, the cache will be recalculated when this value is changed." --> 

<t id="113"></t> 

<!-- [114] "Cache: Proxy Disk Cache Keep without Content-Length" --> 

<t id="114"></t> 

<!-- [115] "Keep files without Content-Length header information in the cache?" --> 

<t id="115"></t> 

<!-- [116] "Cache: Proxy Disk Cache Refreshes on Last-Modified" --> 

<t id="116"></t> 

<!-- [117] "If set, refreshes files without Expire header information when they have reached double the age they had when they got cached. This may be useful for some regularly updated docs as online newspapers." --> 

<t id="117"></t> 

<!-- [118] "Cache: Proxy Disk Cache Last resort (in days)" --> 

<t id="118"></t> 

<!-- [119] "How many days shall files without Expires and without Last-Modified header information be kept?" --> 

<t id="119"></t> 

<!-- [120] "Cache: Proxy Disk Cache Garbage collector logfile" --> 

<t id="120"></t> 

<!-- [121] "Information about garbage collector runs, removed and refreshed files, cache and disk status goes here." --> 

<t id="121"></t> 

<!-- [122] "PID file" --> 

<t id="122"></t> 

<!-- [123] "In this file, the server will write out it's PID, and the PID of the start script. $pid will be replaced with the pid, and $uid with the uid of the user running the process. 

<br />Note: It can be overridden by the command line option." --> 

<t id="123"></t> 

<!-- [124] "Identify, Use default identification string" -->