From 23fbb26b04921f98c78c600506fa754914f76af2 Mon Sep 17 00:00:00 2001
From: Micael Karlberg When using ssl, there are several alternatives.
+ Defaults to
remotehost ++remotehost Remote rfc931 The client's remote username (RFC 931). authuser - The username with which the user authenticated himself. + The username with which the user authenticated + himself. [date] Date and time of the request (RFC 1123). "request" - The request line exactly as it came from the client(RFC 1945). + The request line exactly as it came from the client + (RFC 1945). status - The HTTP status code returned to the client (RFC 1945). + The HTTP status code returned to the client + (RFC 1945). bytes The content-length of the document transferred.@@ -286,10 +295,11 @@ bytesThe
-combined format is on line that look like this:remotehost rfc931 authuser [date] "request" status bytes "referer" "user_agent" "referer" ++"referer" The url the client was on before - requesting your url. (If it could not be determined a minus - sign will be placed in this field) + requesting your url. (If it could not be determined + a minus sign will be placed in this field) "user_agent" The software the client claims to be using. (If it could not be determined a minus sign will be placed in @@ -389,6 +399,31 @@ bytes and an access to http://your.server.org/image/foo.gif would refer to the file /ftp/pub/image/foo.gif. +{re_write, {Re, Replacement}} + +- Where Re = string() and Replacement = string(). + The ReWrite property allows documents to be stored in the local file + system instead of the document_root location. URLs are rewritten + by re:replace/3 to produce a path in the local filesystem. + For example: + +
+{re_write, {"^/[~]([^/]+)(.*)$", "/home/\\1/public\\2"}
+ + and an access to http://your.server.org/~bob/foo.gif would refer to + the file /home/bob/public/foo.gif. + + In an Apache like configuration file the Re is separated + from Replacement with one single space, and as expected + backslashes do not need to be backslash escaped so the + same example would become: + +ReWrite ^/[~]([^/]+)(.*)$ /home/\1/public\2
+ + Beware of trailing space in Replacement that will be used. + If you must have a space in Re use e.g the character encoding +\040
seere(3) . +{directory_index, [string()]} - @@ -408,7 +443,7 @@ bytes
- CGI properties - requires mod_cgi
+CGI properties - requires mod_cgi
{script_alias, {Alias, RealName}} - Where Alias = string() and RealName = string(). @@ -423,6 +458,19 @@ bytes the server to run the script /web/cgi-bin/foo.
+{script_re_write, {Re, Replacement}} +- Where Re = string() and Replacement = string(). + Has the same behavior as the ReWrite property, except that + it also marks the target directory as containing CGI + scripts. URLs with a path beginning with url-path are mapped to + scripts beginning with directory-filename, for example: + +
+{script_re_write, {"^/cgi-bin/(\\d+)/", "/web/\\1/cgi-bin/"}
+ + and an access to http://your.server.org/cgi-bin/17/foo would cause + the server to run the script /web/17/cgi-bin/foo. +{script_nocache, boolean()} - -- cgit v1.2.3