Roxen.git / server / base_server / configuration.pike

version» Context lines:

Roxen.git/server/base_server/configuration.pike:1:   // This file is part of Roxen WebServer.   // Copyright © 1996 - 2009, Roxen IS.   //      // @appears Configuration   //! A site's main configuration    - constant cvs_version = "$Id: configuration.pike,v 1.720 2011/12/21 00:46:45 jonasw Exp $"; + constant cvs_version = "$Id: configuration.pike,v 1.721 2012/01/18 12:55:26 jonasw Exp $";   #include <module.h>   #include <module_constants.h>   #include <roxen.h>   #include <request_trace.h>   #include <timers.h>      #define CATCH(P,X) do{mixed e;if(e=catch{X;})report_error("While "+P+"\n"+describe_backtrace(e));}while(0)      // Tell Pike.count_memory this is global.   constant pike_cycle_depth = 0;
Roxen.git/server/base_server/configuration.pike:4818:   for all kinds of messages. If an unknown or inapplicable specifier is   encountered it typically expands to '<code>-</code>', but in some   cases it expands to a dummy value that is syntactically compatible   with what it usually expands to.</p>      <p>For compatibility, underscores ('_') may be used wherever   hyphens ('-') occur in the specifier names.</p>      <h3>Format specifiers for both access and event logging</h3>    - <table><tbody valign='top'> + <table class='hilite-1stcol'><tbody valign='top'>   <tr><td>\\n \\t \\r</td>    <td>Insert a newline, tab or linefeed character, respectively.</td></tr>   <tr><td>$char(int)</td>    <td>Insert the (1 byte) character specified by the integer. E.g.    '<code>$char(36)</code>' inserts a literal '<code>$</code>'    character.</td></tr>   <tr><td>$wchar(int)</td>    <td>Insert the specified integer using 2 bytes in network byte    order. Specify a negative integer to get the opposite (i.e. big    endian) order.</td></tr>
Roxen.git/server/base_server/configuration.pike:4866:   <tr><td>$server-cputime</td>    <td>Server cpu (user+system) time in milliseconds.</td></tr>   <tr><td>$server-usertime</td>    <td>Server cpu user time in milliseconds.</td></tr>   <tr><td>$server-systime</td>    <td>Server cpu system time in milliseconds.</td></tr>   </tbody></table>      <h3>Format specifiers for access logging</h3>    - <table><tbody valign='top'> + <table class='hilite-1stcol'><tbody valign='top'>   <tr><td>$host</td>    <td>The remote host name, or ip number.</td></tr>   <tr><td>$vhost</td>    <td>The Host request-header sent by the client, or '-' if none.</td></tr>   <tr><td>$ip-number</td>    <td>The remote ip number.</td></tr>   <tr><td>$bin-ip-number</td>    <td>The remote host ip as a binary integer number.</td></tr>   <tr><td>$xff</td>    <td>The remote host name/ip taken from the X-Forwarded-For header, or
Roxen.git/server/base_server/configuration.pike:4949:    otherwise '0'.</td></tr>   <tr><td>$content-type</td>    <td>Resource MIME type.</td></tr>   <tr><td>$cookies</td>    <td>All cookies sent by the browser, separated by ';'.</td></tr>      <tr><td>$cache-status</td>    <td>A comma separated list of words (containing no whitespace)    that describes how the request got handled by various caches:    -  <table><tbody valign='top'> +  <table class='hilite-1stcol'><tbody valign='top'>    <tr><td>protcache</td>    <td>The page is served from the HTTP protocol cache.</td></tr>    <tr><td>protstore</td>    <td>The page is stored in the HTTP protocol cache.</td></tr>    <tr><td>stale</td>    <td>There is a stale entry in the HTTP protocol cache. A    refresh is underway in the background and the stale entry is    sent in the meantime to avoid a long response time and server    congestion.</td></tr>    <tr><td>refresh</td>    <td>This is the finishing of the background refresh request    for the entry in the HTTP protocol cache.</td></tr>    <tr><td>pcoderam</td>    <td>A hit in the RXML p-code RAM cache.</td></tr>    <tr><td>pcodedisk</td>    <td>A hit in the RXML p-code persistent cache.</td></tr> -  +  <tr><td>pcodestore</td> +  <td>P-code is added to or updated in the persistent cache.</td></tr> +  <tr><td>pcodestorefailed</td> +  <td>An attempt to add or update p-code in the persistent cache +  failed (e.g. due to a race with another request).</td></tr>    <tr><td>cachetag</td>    <td>RXML was evaluated without any cache miss in any RXML    &lt;cache&gt; tag. The &lt;nocache&gt; tag does not count as a    miss.</td></tr>    <tr><td>xsltcache</td>    <td>There is a hit XSLT cache.</td></tr>    <tr><td>nocache</td>    <td>No hit in any known cache, and not added to the HTTP    protocol cache.</td></tr>    </tbody></table></td></tr>      <tr><td>$eval-status</td>    <td>A comma separated list of words (containing no whitespace)    that describes how the page has been evaluated:    -  <table><tbody valign='top'> +  <table class='hilite-1stcol'><tbody valign='top'>    <tr><td>xslt</td>    <td>XSL transform.</td></tr>    <tr><td>rxmlsrc</td>    <td>RXML evaluated from source.</td></tr>    <tr><td>rxmlpcode</td>    <td>RXML evaluated from compiled p-code.</td></tr>    </tbody></table></td></tr>      <tr><td>$protcache-cost</td>    <td>The lookup depth in the HTTP protocol module low-level cache.</td></tr>
Roxen.git/server/base_server/configuration.pike:5007:   below.</p>      <dl>   <dt>Facility: roxen</dt>    <dd><p>This is logging for systems in the Roxen WebServer core.    For logging that is not related to any specific configuration, the    configuration for the Administration Interface is used.</p>       <p>The known events are:</p>    -  <table><tbody valign='top'> +  <table class='hilite-1stcol'><tbody valign='top'>    <tr><td>ram-cache-gc</td>    <td>Logged after the RAM cache GC has run. $handle-time and    $handle-cputime are set to the time the GC took (see    descriptions above for details).</td></tr>    <tr><td>ram-cache-rebase</td>    <td>Logged when the RAM cache has performed a rebias of the    priority queue values. Is a problem only if it starts to    happen too often.</td></tr>    </tbody></table></dd>   
Roxen.git/server/base_server/configuration.pike:5035:       <p>The action <code>crawl-file</code> is logged for files that are    crawled by the persistent cache crawler.</p>       <p>The actions <code>file-change</code> and    <code>dir-change-flat</code> are logged when external file and    directory changes are detected (and this feature is enabled).</p>       <p>These extra format specifiers are defined where applicable:</p>    -  <table><tbody valign='top'> +  <table class='hilite-1stcol'><tbody valign='top'>    <tr><td>$ac-userid</td>    <td>The ID number of the AC identity whose edit area was used.    Zero for the common view area.</td></tr>    <tr><td>$workarea</td>    <td>The unique tag for the work area. Empty for the main work    area.</td></tr>    <tr><td>$commit-type</td>    <td>The type of file commit, one of <code>create</code>,    <code>edit</code>, <code>delete</code>, and    <code>undelete</code>.</td></tr>