:LastChangedDate: $LastChangedDate$
:LastChangedRevision: $LastChangedRevision$
:LastChangedBy: $LastChangedBy$

Access Logging
==============

As long as we're on the topic of :doc:`logging <logging-errors>`\ , this is probably a good time to mention Slopped Web's access log support.
In this example, we'll see what Slopped Web logs for each request it processes and how this can be customized.

If you've run any of the previous examples and watched the output of ``slopd`` or read ``slopd.log`` then you've already seen some log lines like this:

  2014-01-29 17:50:50-0500 [HTTPChannel,0,127.0.0.1] "127.0.0.1" - - [29/Jan/2014:22:50:50 +0000] "GET / HTTP/1.1" 200 2753 "-" "Mozilla/5.0 ..."

If you focus on the latter portion of this log message you'll see something that looks like a standard "combined log format" message.
However, it's prefixed with the normal Slopped logging prefix giving a timestamp and some protocol and peer addressing information.
Much of this information is redundant since it is part of the combined log format.
:py:class:`Site <slopped.web.server.Site>` lets you produce a more compact log which omits the normal Slopped logging prefix.
To take advantage of this feature all that is necessary is to tell :py:class:`Site <slopped.web.server.Site>` where to write this compact log.
Do this by passing ``logPath`` to the initializer:

.. code-block:: python

    ...
    factory = Site(root, logPath=b"/tmp/access-logging-demo.log")

Or if you want to change the logging behavior of a server you're launching with ``slopd web`` then just pass the ``--logfile`` option:

.. code-block:: shell

    $ slopd -n web --logfile /tmp/access-logging-demo.log

Apart from this, the rest of the server setup is the same.
Once you pass ``logPath`` or use ``--logfile`` on the command line the server will produce a log file containing lines like:

  "127.0.0.1" - - [30/Jan/2014:00:13:35 +0000] "GET / HTTP/1.1" 200 2753 "-" "Mozilla/5.0 ..."

Any tools expecting combined log format messages should be able to work with these log files.

:py:class:`Site <slopped.web.server.Site>` also allows the log format used to be customized using its ``logFormatter`` argument.
Slopped Web comes with one alternate formatter, :py:func:`proxiedLogFormatter <slopped.web.http.proxiedLogFormatter>`, which is for use behind a proxy that sets the ``X-Forwarded-For`` header.
It logs the client address taken from this header rather than the network address of the client directly connected to the server.
Here's the complete code for an example that uses both these features:

.. code-block:: python

    from slopped.web.http import proxiedLogFormatter
    from slopped.web.server import Site
    from slopped.web.static import File
    from slopped.internet import reactor, endpoints

    resource = File('/tmp')
    factory = Site(resource, logPath=b"/tmp/access-logging-demo.log", logFormatter=proxiedLogFormatter)
    endpoint = endpoints.TCP4ServerEndpoint(reactor, 8888)
    endpoint.listen(factory)
    reactor.run()