<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>

<!-- Generated by BuildHTML 1.10f (31-Jul-2001) -->

<!-- This document contains universally accessible HTML markup conforming to the above W3C Document Type Description (DTD) -->

<head>

<title>Website Log Checker v1.00j</title>

</head>

<body>

<h1>Website Log Checker<br />

<small><i>PhunLogCK v1.00j</i></small></h1>

<p>This application will analyse server logs and output a meaningful CSV file
('LogCheck'). It also recognises submitted 'form' information and will output
a separate CSV file ('FormInfo') if any is found. If the 'Suppress Corrupt/Hack Forms' button is unticked, details will appear in this file.

<p>If the option 'Weekly Summary' is ticked, it will output a tabulated
'Weekly Summary of Pages Served', in the file 'WkSummary'.

<p>The default output filenames 'LogCheck','FormInfo' and 'WkSummary' are
supplemented by the final numeric character of the log filename if it exists.

<p>All summary information is displayed in the application's window on
completion of analysis.

<p>The program was developed using the logs supplied by 'enterprise.net', who
name the current log 'transfer_log', with up to 4 earlier versions
('transfer_log','transfer_log/0','transfer_log/1' etc.).

<h2>Output</h2>

<p> Output from the program is in four sections:

<h3>Summary of HTML Pages Transferred</h3>

<p>'Summary of HTML Pages Transferred' contains a chronological list of all
pages served.

<h3>Summary of Transfers</h3>

<p>'Summary of Transfers' is a summary of all files transferred, subdivided
by type.

<h3>Ancillary Information</h3>

<p>'Ancillary Information' lists further useful information:

<ul>

<li>'Robot Requests' is incremented when requests are received for pages by
known robots. The application maintains an internal list of robots, in the
file 'Robots'. To become 'known', a robot must first request a file
'robots.txt' from the root directory of the server.

<li>'FAVICON Requests' is incremented when a MSIE user asks for this file.
Presumably this means they like your site!

<li>'Cache Requests' is incremented where the requesting domain contains the
word 'cache'.

<li>'Form Submissions' is incremented when form input is detected, and the
data found is output to the separate file 'FormInfo'.

<li>'Corrupt requests/hacks' refers to attempts to transfer or execute files
to which access may be forbidden or which may not exist. These are detected
in the form handling routines.

<li>'Bytes Transferred' gives a total byte count of all files transferred.

</ul>

<h3>HTTP Transactions</h3>

<p>Following each request from remote domains, a transaction status code is
given. In normal circumstances this is '200', and is not reported in the log
summary. All codes received are counted, but only those other than '200' and
which affect pages are reported in the summary of HTML pages. The reports
correspond to those contained in RFC 2616 (HTTP/1.1).

<ul>

<li>'Informational' (Transaction Codes 100-101) 

<li>'Successful (OK)' (Transaction Codes 200-206)

<li>'Redirection' (Transaction Codes 300-307)

<li>'Client Errors' (Transaction Codes 400-417) gives a count of all client
errors, such as requests for non-existent files.

<li>'Server Errors' (Transaction Codes 500-505) gives a count of all server
errors.

</ul>

<h3>Page Hit Counts</h3>

<p>'Page Hit Counts' summarises all page transfers, by page. The application
maintains an internal list of pages, in the file 'Pages'. At the end, a
summary is given. The last item, 'Average Daily Page Throughput' is based on
pages per minute, so it should give a fairly accurate picture of the daily
throughput of your site unless the log is for an unrepresentatively short
period.

<h2>To Do</h2>

<p>At the moment neither the 'Robots' or 'Pages' file is sorted. I may add
routines to do this. In the meantime, once all your pages have been 'seen'
the list can be sorted in <A HREF="http://zap.eu.org/">!Zap</A> or whatever.

<p><i>&copy; I.W. Logan, 20 November 2001<br>
 &nbsp;revised 16 October 2003</i>

</body>

</html>

