Antwort: Re: Antwort: Re: Antwort: Re: Antwort: [Mod_gzip] mod_gzip and solaris 9

Fri, 08 Aug 2003 17:03:25 +0100

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
 <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
no, Apache writes standard access stuff to its access_log file and only
those items specified in the CustomLog directive within the mod_gzip
configuration to the mod_gzip_log file. 
 
Therefore, if its serving requests AND passing them through mod_gzip,
it will write to both log files (as it does on our Linux servers). If
its serving requests but NOT passing them though mod_gzip, then the
mod_gzip log will remain empty - the access log itself will continue to
record access attempts and requests. 
 
There IS therefore a "specific mod_gzip log file" as its the one that
writes the mod_gzip info. Regardless of whether its apache or the
module that writes it, it IS specific to mod_gzip in this respect. so,
in the way I am phrasing things here, there is an APACHE log file that
records http requests etc and a MODGZIP log file that records the
compression statistics! 
 
<a class="moz-txt-link-abbreviated" href="mailto:Michael.Schroepl@telekurs.de">Michael.Schroepl@telekurs.de</a> wrote: 
<blockquote type="cite"
 cite="midC1256D7C.00542F7C.00@detkw004.dnotes.telekurs.com">
 <pre wrap="">Hi,

  </pre>
  <blockquote type="cite">
    <pre wrap="">ah, I see we're getting confused here......&lt;br&gt;
the Apache log file itself (/var/log/http/access_log) is fine and does
indeed log everything.&lt;br&gt;
It the specific mod_gzip logfile (the one that records the compression
ratios etc - /var/log/httpd/mod_gzip_log)&amp;nbsp; that is not being written
to, implying that it is ignoring the content for some reason.....&lt;br&gt;
    </pre>
  </blockquote>
  <pre wrap=""><!---->
nope. There is no such thing as a "specific mod_gzip logfile".

You can have any number of Apache log files, and you specify them
with Apache directives that have nothing to do with mod_gzip.
It is Apache who decides whether to write a log entry, not mod_gzip.

The only thing that involves mod_gzip here is that this module can
fill certain "notes" inside the Apache that can then serve as columns
of a log entry, thus logging information about mod_gzip's operation.

If mod_gzip isn't available, then the content of these columns will
be empty (mostly "-"), but this will not prevent the log entry from
being created.

Regards, Michael

_______________________________________________
mod_gzip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mod_gzip@lists.over.net">mod_gzip@lists.over.net</a>
<a class="moz-txt-link-freetext" href="http://lists.over.net/mailman/listinfo/mod_gzip">http://lists.over.net/mailman/listinfo/mod_gzip</a>

_____________________________________________________________________
This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit <a class="moz-txt-link-freetext" href="http://www.mci.com">http://www.mci.com</a>
  </pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<table border="0" width="300">
  <tbody>
    <tr>
      <td><font color="#4545ab"><b>Matthew Claridge</b></font></td>
    </tr>
    <tr>
      <td><font color="#5757bb">Product Support Engineer<br>
RWA Limited<br>
Direct line: 02920 815 054<br>
Email: <a class="moz-txt-link-abbreviated" href="mailto:mclaridge@rwa-net.co.uk">mclaridge@rwa-net.co.uk</a><br>
Web: <a class="moz-txt-link-abbreviated" href="http://www.rwa-net.co.uk">www.rwa-net.co.uk</a></font></td>
    </tr>
  </tbody>
</table>
</div>
</body>
</html>