Can anyone explain this stuff in my apache error_log please

This is pyblosxom related!

I use "print >>sys.stderr" in a plugin I'm writing to log information
to the apache error_log file.  This is on a home desktop system so
it's a quite acceptable (and easy) way of getting debug information
while writing code.

I have recently changed from Slackware to Fedora and at the same time
have now got a much newer version of apache.  I'm now seeing stuff
like the following in my apache error_log:-

    [Wed Oct 10 08:55:43 2007] [error] [client 193.128.168.194] fullPath is  /home/chris/webdev/info/
    [Wed Oct 10 08:55:43 2007] [error] [client 193.128.168.194] editFile is /home/chris/webdev/info//index.rst
    [Wed Oct 10 08:55:50 2007] [error] [client 193.128.168.194] fullPath is  /home/chris/webdev/info/Home/index, referer: http://home.isbd.net/cgi-bin/pyblosxom.cgi
    [Wed Oct 10 08:55:50 2007] [error] [client 193.128.168.194] editFile is /home/chris/webdev/info/Home/index.rst, referer: http://home.isbd.net/cgi-bin/pyblosxom.cgi

What's the producer/cause of those second two lines with "referer:"
in them?  As far as I know my plugin python is only writing the first
two and somehow python/apache/pyblosxom is adding the second two.
More to the point why are the values of 'fullPath' and 'editFile'
different?  The second two lines are followed by a full error traceback 
of several lines to an error that relates to the 'wrong' values of 
fullPath and editFile.


This may relate to another problem I have, the plugin works perfectly
when run using firefox on my home system (i.e. where pyblosxom and the
apache server are) but is failing when run using Firefox from a remote
system, though it's still a Fedora 7 system.  I.e. when I run my
pyblosxom plugin using the browser at home I only see the first two of 
the lines shown above in the apache error_log, it's only when I run
it from a remote firefox that the second two lines and the error
traceback appear (and pyblosxom diaplays an error message rather 
than the expected page).

-- 
Chris Green

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/