Stories
Slash Boxes
Comments

Slash Open Source Project

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • After recently upgrading from 2.0.0 to 2.2.4, I went ahead and installed mod_gzip last night. I am using just the basic configuration given as an example on the mod_gzip site. So far I have not seen any problems. I can definitely see a speed increase though, it seems twice as fast.

    I did not add anything to any of the virtual host sections, is that necessary?
    • Can you post that config?

      --

      --
      You can't grep a dead tree.
      • I thought Slashdot and Slashcode were using it all this time! Had I known you weren't using it, I probably would not have tried it. I got the "minimum 'safe' configuration" from the mod_gzip site:

        http://www.remotecommunications.com/apache/mod_g zi p/src/1.3.19.1a/samples.txt

        I just copied this into a file and included it in httpd.conf like slash.conf is included, such as:

        Include /usr/local/apache/conf/mod_gzip.conf

        The first config is:

        *** MINIMUM 'SAFE' CONFIGURATION...
        *** This will only compress text/html and text/plain MIME types...

        Submitted by: Kevin Kiley 02/21/01

        The minimum 'safe' set of configuration commands for
        the 1.3.17.x series would still look like the following...

        # [ mod_gzip sample configuration ]

        # 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.
        #
        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

        # [End of mod_gzip sample config]
        • by davidt (71) on Thursday January 17 2002, @12:59AM (#4034) Homepage
          never mind the last config, after some research I see that it doesn't do a whole lot. The speed increase probably has more to do with an upgrade at my ISP that occured on the same day.

          I have modified the config to include .pl files and had to exclude the two reqheader content types that are mentioned elsewhere in the comments. I think it's working - but am not sure about the actual performance gain.