30.01.2015 Views

Administrator's Guide - Kerio Software Archive

Administrator's Guide - Kerio Software Archive

Administrator's Guide - Kerio Software Archive

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Logs<br />

Note:<br />

1. Only accesses to allowed pages are recorded in the HTTP log. Request that were blocked<br />

by HTTP rules are logged to the Filter log (see chapter 22.9), if the Log option is enabled<br />

in the particular rule (see section 13.2).<br />

2. The Http log is intended to be processes by external analytical tools. The Web log (see<br />

bellow) is better suited to be viewed by the <strong>Kerio</strong> Control administrator.<br />

An example of an HTTP log record in the Apache format:<br />

192.168.64.64 - jflyaway<br />

[18/Apr/2008:15:07:17 +0200]<br />

"GET http://www.kerio.com/ HTTP/1.1" 304 0 +4<br />

• 192.168.64.64 — IP address of the client host<br />

• rgabriel — name of the user authenticated through the firewall (a dash is<br />

displayed if no user is authenticated through the client)<br />

• [18/Apr/2008:15:07:17 +0200] — date and time of the HTTP request. The +0200<br />

value represents time difference from the UTC standard (+2 hours are used in this<br />

example — CET).<br />

• GET — used HTTP method<br />

• http://www.kerio.com — requested URL<br />

• HTTP/1.1 — version of the HTTP protocol<br />

• 304 — return code of the HTTP protocol<br />

• 0 — size of the transferred object (file) in bytes<br />

• +4 — count of HTTP requests transferred through the connection<br />

300

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!