Your message dated Tue, 3 Jul 2007 16:11:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libapache-mod-gzip
Version: 1.3.19.1a-5
Severity: normal
I have mod_gzip configured for my apache server at www.buberel.org.
My configuration is as follows:
# mod_gzip is the last module in the module list
LoadModule gzip_module /usr/lib/apache/1.3/mod_gzip.so
<IfModule mod_gzip.c>
mod_gzip_on Yes
mod_gzip_can_negotiate Yes
mod_gzip_command_version '/gzip/mod_gzip_status'
mod_gzip_temp_dir /tmp
mod_gzip_keep_workfiles No
mod_gzip_minimum_file_size 500
mod_gzip_maximum_file_size 500000
mod_gzip_maximum_inmem_size 60000
mod_gzip_min_http 1000
mod_gzip_dechunk Yes
mod_gzip_item_include uri ^/.*\.php.*$
mod_gzip_item_include uri ^/.*\.html.*$
mod_gzip_item_include uri ^/.*\.css.*$
mod_gzip_item_include mime ^text/
mod_gzip_item_include mime ^application/x-httpd-php
mod_gzip_item_exclude mime ^image/
LogFormat "%h %l %u %t \"%V %r\" %<s %b mod_gzip:
%{mod_gzip_result}n In:%{mod_gzip_input_size}n -< Out:%{mod_gzip_output_size}n
= %{mod_gzip_compression_ratio}n pct." common_with_mod_gzip_info2
CustomLog /usr/local/web/buberel-ssl/logs/mod_gzip.log
common_with_mod_gzip_info2
mod_gzip_add_header_count Yes
</IfModule>
When the server is started, an empty mod_gzip.log file is created in the
specified
directory (/usr/local/web/buberel-ssl/logs/mod_gzip.log). However, as pages
(php, css,
html, and images) are requested from the server, no log entries are written to
the file.
The log file that is created has root.root privs, although the server runs as
www-data.
I changed ownership of the file to www-data, but that did not improve the
situation.
I have even tried changing the permissions on the file to a+rw, to no avail.
The configuration described above has been used successfully by me on solaris
with
apache 1.3.19 and the exact same version of mod_gzip (1.3.19.1a). Invoking the
status
command (http://www.buberel.org/gzip/mod_gzip_status) returns the following:
mod_gzip is available...
mod_gzip_version = 1.3.19.1a
mod_gzip_on = Yes
Even if my include/exclude filters were done incorrectly, I would expect to see
log file
entries indicating the requests were EXCLUDED by mod_gzip and not compressed.
So far,
I have not seen any entries in the log file.
-jason
[EMAIL PROTECTED]
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux taylor 2.4.20 #4 Tue Jul 29 10:17:58 PDT 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages libapache-mod-gzip depends on:
ii apache-common 1.3.26-0woody3 Support files for all Apache webse
ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an
ii libdb2 2:2.7.7.0-7 The Berkeley database routines (ru
ii libexpat1 1.95.2-6 XML parsing C library - runtime li
--- End Message ---
--- Begin Message ---
This package has been removed from Debian unstable. I'm therefore
closing this bug report. The package has been removed because it
was for Apache 1 only and not maintained anymore.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
