Webhosting Weblogs: Difference between revisions

From AAISP Support Site
No edit summary
m (clean up, typos fixed: apache → Apache, etc, → etc.,)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
[[File:Couk.png|link=:Category:Webhosting]]


You can access logs of all web access to your site. These are available as text files listing every access so you can perform your own analysis, and as a graphical summary. The logs are held for each month.
You can access logs of all web access to your site. These are available as text files listing every access so you can perform your own analysis, and as a graphical summary. The logs are held for each month.


Line 16: Line 13:


We aim to keep the logs for as long as practical, but it is recommended that you should download the previous months logs and store them yourself if you would like to retain a copy. You can download the raw log file using ftp. We currently remove old logs after one year.
We aim to keep the logs for as long as practical, but it is recommended that you should download the previous months logs and store them yourself if you would like to retain a copy. You can download the raw log file using ftp. We currently remove old logs after one year.

==Log format==
It is not an Apache style of format, but the fields are as follows

Host (i.e. site name)
IP address
Bytes received (i.e. the request or uploaded data)
Bytes sent (i.e. the web page, etc., sent)
Response/error code (i.e. 200 for served page)
From
Auth
When
Method (e.g. GET/POST)
Request (i.e. the page)
Path (i.e. on the end of the script name)
Params
Query (after ?)
Fragment (after #, so never sent by browser anyway!)
Version
Agent
Referrer
Cookie



==Alternatives==
==Alternatives==



Having said this, customers tend to prefer to use third-party solutions for their web stats, such as Google Analytics (among others).
Having said this, customers tend to prefer to use third-party solutions for their web stats, such as Google Analytics (among others).


==Other Webhosting pages:==
==Other Webhosting pages==
<ncl style=bullet maxdepth=5 headings=bullet headstart=2 showcats=1 showarts=1>Category:Webhosting</ncl>
<ncl style=bullet maxdepth=5 headings=bullet headstart=2 showcats=1 showarts=1>Category:Webhosting</ncl>


Line 27: Line 48:




[[Category:Webhosting]]
[[Category:Webhosting|Weblogs]]
[[Category:Domains]]

Latest revision as of 00:08, 15 March 2017

You can access logs of all web access to your site. These are available as text files listing every access so you can perform your own analysis, and as a graphical summary. The logs are held for each month.

To set up web logging, follow these simple steps.

  1. Using ftp, create on your site a directory called weblog
  2. Using a browser, access any page on your site
  3. Using ftp you should see a file in the weblog directory named by the month, e.g. 2008-10 for October 2008
  4. You can download this file at any time for any month using ftp. You can also delete old months using ftp.
  5. You can also access the page via your web site, e.g. /weblog/2008-10 which will show you a graphical summary
  6. You can also access the web log selectively, e.g. /weblog/2008-10/01 where the part at the end (01 in that case) has to match either the start of the date or the start of the URL. This can be useful as very big monthly logs may be too big to produce a report within the time allowed for CGI scripts.
  7. If you want to stop other people accessing the logs via the web site, create a password.txt file in the weblog directory (see above).
  8. You can create a weblog directory in any part of your site, and access to that part of the site is logged.

We aim to keep the logs for as long as practical, but it is recommended that you should download the previous months logs and store them yourself if you would like to retain a copy. You can download the raw log file using ftp. We currently remove old logs after one year.

Log format

It is not an Apache style of format, but the fields are as follows

Host (i.e. site name)
IP address
Bytes received (i.e. the request or uploaded data)
Bytes sent (i.e. the web page, etc., sent)
Response/error code (i.e. 200 for served page)
From
Auth
When
Method (e.g. GET/POST)
Request (i.e. the page)
Path (i.e. on the end of the script name)
Params
Query (after ?)
Fragment (after #, so never sent by browser anyway!)
Version
Agent
Referrer
Cookie


Alternatives

Having said this, customers tend to prefer to use third-party solutions for their web stats, such as Google Analytics (among others).

Other Webhosting pages

<ncl style=bullet maxdepth=5 headings=bullet headstart=2 showcats=1 showarts=1>Category:Webhosting</ncl>

Webhosting Service page on our main website