Accesslog Format Options; Table 28 Accesslog Format Options - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Controller Administrator's Guide
show accesslog
List access log settings.
Note!
Media Flow Controller accesslog is enabled by default and cannot be disabled.
Note!
View the Media Flow Controller accesslog through the Web interface, Logs > Service
Log page.

accesslog format Options

We recommend that you do not change the default format as it conforms to NCSA standard,
followed by APACHE, SQUID and so forth; however, you may do so if you wish. Media Flow
Controller is capable of tracking all the fields described. Options are given in
combination).
Table 28
Accesslog Format Options
(RFC 931 authentication server) The username associated with the client connection, determined
%9
(Bytes Out No Header) (default) The size of the object returned to the client, not including the
%b
(cache_hit)
%c
(filename)
%f
(remote_host)
%h
(header)
%i
(request_method)
%m
(response_header)
%o
(query_string)
%q
(request_line) (default)
%r
(status) (default)
%s
Field
from an Ident (RFC 931) server running on the client host.
response headers. If no content was returned to the client, this value
is "-" (dash).
Shows from where the object is delivered; for example, Buffer (from
buffer cache), Origin (from origin), Tunnel (from tunnel path), SSD
(from SSD disk), SAS (from SAS disk), SATA (from STAT disk), NFS
(from NFS manager), TFM (from temporary file manager).
The requested filename. Not supported in Release 2.0.4.
The IP address of the client (remote host) that made the request.
The IP address reported here is not necessarily the address of the
machine at which the user is sitting. If a proxy server exists between
the user and the server, this address is the address of the proxy,
rather than the originating machine.
Contents of header lines in the request sent to the server.
The method the incoming request used.
Contents of the header lines in the response.
The query string; prepended with a ? if a query string exists,
otherwise an empty string.
The request line from the client, including the method, path, query-
string, and protocol; this is equivalent to %m %U %H.
The request status code the server sends back to the client:
•  
•  
•  
See
Media Flow Controller CLI Commands
Description
Successful response (codes begin at 2),
Redirection (codes begin at 3),
Error (at client, codes begin at 4), at Server (codes begin at 5).
"Status/Error Codes" on page 210
Table 28
(use any
for more details.
accesslog format Options
291

Advertisement

Table of Contents
loading

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents