Databases Reference
In-Depth Information
Compression with the APEX Listener
If you use
YSlow
to examine an APEX page while accessing it through the APEX Listener, you will see that,
as shown in Figure 1-35, in a standalone deployment, by default, the resources are not compressed, nor
do they have expiry headers associated with them.
Figure 1-35.
Examining APEX Listener with YSlow
So, what are the options? Well, it appears that the APEX listener does support compression, there is
just not currently an option in the configuration screens to enable it. You need to drop down to editing
the configuration file manually to do that.
What I typically do is use the previous process to fire up the APEX Listener and quickly configure it.
Once I'm happy, I copy the configuration file it created and store it somewhere locally. If you didn't
notice, when you started up the APEX Listener it created the configuration directory in a “random”
directory (the directory used will depend on your environment and may not match mine). In my case it
was
INFO: Extracting to: /var/folders/mN/mNPteN52HoqHK2miZ4o6IU+++TU/-Tmp-/apex
By looking at the output in your startup you should be able to navigate to that directly and find the
apex-config.xml
file:
[jes@ae1 ~]$ cd /var/folders/mN/mNPteN52HoqHK2miZ4o6IU+++TU/-Tmp-/apex
[jes@ae1 apex]$ ls -al
total 24
drwxr-xr-x 7 jes staff 238 19 Feb 13:39 .
drwx------ 10 jes staff 340 19 Feb 14:53 ..
drwxr-xr-x 7 jes staff 238 19 Feb 12:49 apex
-rw-r--r-- 1 jes staff 2727 19 Feb 13:39 apex-config.xml
-rw-r--r-- 1 jes staff 63 19 Feb 13:01 apex.properties
drwxr-xr-x 6 jes staff 204 19 Feb 13:02 bdb
-rw-r--r-- 1 jes staff 258 19 Feb 13:02 credentials
