1a8dbabb03
-- mod_gzip transparently compresses the output of apache to client browsers. It uses the 'Accept-Encoding' header to determine whether or not the client browser wants gzipped content.
98 lines
3.3 KiB
Plaintext
98 lines
3.3 KiB
Plaintext
# mod_gzip_on [Yes/No]
|
|
#
|
|
# Use this command to turn mod_gzip 'on' or 'off'.
|
|
# The command can go into the base server configuration
|
|
# or be used to control if mod_gzip is active inside
|
|
# any particular virtual directory or host section.
|
|
#
|
|
mod_gzip_on Yes
|
|
|
|
# mod_gzip_item_include type regular_expression
|
|
# mod_gzip_item_exclude type regular_expression
|
|
#
|
|
# Use 'include' and 'exclude' commands to specify which
|
|
# items are eligible for compression.
|
|
#
|
|
# The valid values for 'type' field are...
|
|
#
|
|
# file, mime, handler, reqheader, rspheader.
|
|
#
|
|
# The 3rd parameter must be a valid 'regular expression'
|
|
# which will be used to 'match' the requested item(s).
|
|
#
|
|
mod_gzip_item_include file \.htm$
|
|
mod_gzip_item_include file \.html$
|
|
mod_gzip_item_include mime text/.*
|
|
|
|
# NOTE: The following entry was required to compress negotiated
|
|
# home pages in version 1.3.17.1a but is now only needed
|
|
# if you would like to compress your directory listings...
|
|
#
|
|
# mod_gzip_item_include mime httpd/unix-directory
|
|
|
|
# mod_gzip_dechunk [Yes/No]
|
|
#
|
|
# If a response is being generated dynamically and
|
|
# the response content generator is always using
|
|
# 'Transfer-Encoding: chunked' then that response
|
|
# cannot normally be 'compressed' since a transport layer
|
|
# encoding is already being applied. The "mod_gzip_dechunk Yes"
|
|
# option will transparently remove all 'chunked' encoding
|
|
# and allow the response to be fully compressed. Certain
|
|
# versions of mod_php will need this option set ON for the
|
|
# dynamic output to be compressed. Whenever possible just
|
|
# make sure this option and the extra step required
|
|
# are NOT needed by making sure the response generator is NOT
|
|
# using 'Transfer-encoding: chunked'.
|
|
#
|
|
mod_gzip_dechunk yes
|
|
|
|
# mod_gzip_min_http [1000/1001/etc...]
|
|
#
|
|
# Only use this to 'block' browsers that don't support a
|
|
# certain minimum level of the HTTP protocol. The option
|
|
# uses the same internal 'numeric' value(s) used by Apache
|
|
# itself to indicate certain HTTP protocol support level(s).
|
|
#
|
|
# 1000=HTTP/1.0 1001=HTTP/1.1, etc.
|
|
#
|
|
# mod_gzip_min_http 1000
|
|
|
|
# mod_gzip_temp_dir /tmp
|
|
#
|
|
# Use this option to specify the directory that mod_gzip should
|
|
# use for workfiles. Do not add a trailing 'slash' to the name.
|
|
#
|
|
# Whenever possible ( and for the best performance ) this 'temporary'
|
|
# workfile directory should be a valid RAMDISK.
|
|
#
|
|
# The directory must already exist when Apache starts.
|
|
#
|
|
# Be sure permissions are set right for whatever directory is
|
|
# used as the 'temp_dir'. The User/Group used by the Server during
|
|
# runtime ( such as 'www' or 'nobody' ) must have read/write
|
|
# access to the directory. If permissions are incorrect then the
|
|
# mod_gzip 'result' string will probably be 'RECOVERY' and your
|
|
# Apache error_log will contain messages about mod_gzip being
|
|
# unable to access work files.
|
|
#
|
|
# If no 'mod_gzip_temp_dir' is specified then the DEFAULTS are...
|
|
#
|
|
# /tmp for UNIX
|
|
# c:\temp for Win32.
|
|
#
|
|
# WARNING: do NOT use /tmp for this purpose, as you could open
|
|
# yourself up to tmp-race attacks. Instead, create a directory
|
|
# with r/w access only for the webserver uid and gid.
|
|
|
|
mod_gzip_temp_dir /tmp
|
|
|
|
# mod_gzip_keep_workfiles [Yes/No]
|
|
#
|
|
# If this option is 'Yes' then mod_gzip will not delete any
|
|
# workfiles it may be generating in the 'mod_gzip_temp_dir'
|
|
# location. Use this option only for diagnostic purposes.
|
|
# The 'default' setting is 'No'.
|
|
#
|
|
mod_gzip_keep_workfiles No
|