Databases Reference
In-Depth Information
Figure 1-12.
Components view in YSlow
Figure 1-12 shows the individual components; in this case I have drilled into the JavaScript files. The
interesting thing to notice here is that
YSlow
shows you the size of each resource, in kilobytes. Also notice
that there is a column for GZIP (KB), which would show the compressed size if the content was in
compressed format. Since we have not enabled gzip compression yet, obviously there is nothing in this
column. However when you do enable compression, you will be able to use
YSlow
to see what kind of
benefit is gained.
Okay, so enough talking, right? Let's get on with enabling gzip on our OHS. The first thing you need
to do is to make sure the gzip module is loaded into your OHS configuration. The installation of
mod gzip
is fairly straightforward and well documented. You simply need to place the module into the directory
containing all your other Apache modules (usually in the
libexec
directory). It's also recommended that
you use the separate configuration file (
mod gzip.conf
) for all the
mod gzip
-related configuration and
include this new configuration file from your main Apache configuration file (
httpd.conf
), rather than
placing the
mod gzip
configuration directly in the main file.
Caution
mod gzip
is not officially supported by Oracle. So if you are the least bit wary of changing the
configuration on your OHS, or you are worried that you may be left in an unsupported position, consider using
another Apache server to proxy requests to the OHS and load the
mod gzip
module on that Apache server instead.
Having said that, we have successfully run
mod gzip
for a long time now without any ill effects. In any case, you
are well advised to try this on a test system before using it on your production setup.
If you look in the
httpd.conf
file you should notice a section where all the modules are loaded. For
example:
