Enhanced Functionality in Service Pack 2

This document describes the Ignore URI Arguments patch for ExceleratorTM version 2.3.0.2.7 and higher.

The Ignore URI Arguments feature applies only to reverse acceleration services. It is not available for forward or transparent proxy services.


Ignore URI Arguments


Overview

Incoming URL requests often include URI arguments---strings that begin with a question mark (?). ISPs commonly use URI arguments for logging or billing purposes.

In many cases, the base URL actually refers to the same object on the origin Web server. However, since Excelerator caches objects by unique URL, the URI arguments cause the same object to be cached multiple times---once for each unique URL.

It is obviously more efficient to cache one object rather than multiple copies of the same object. However, there are situations where retaining the URI arguments is more important than preventing duplicate object caching.

This feature lets you configure the reverse acceleration services that should have the URI arguments stripped from incoming URLs.


Using the Feature


Setting the Option

To configure a reverse acceleration service to ignore URI arguments in incoming URLs, do the following:

  1. At the console prompt, enter the following command:

    set accelerator name discardUriArgument = yes

    where name is the name of the reverse acceleration service you are configuring to ignore URI arguments.

  2. Enter the following command:

    apply


Viewing the Current Option Setting

To view the parameter settings for a reverse acceleration service, do the following:

  1. At the console prompt, enter the following command:

    get accelerator name discarduriargument

    where name is the name of the reverse acceleration service you want to check.


Stripped Arguments Are Not Logged

When a reverse acceleration service is set to ignore URI arguments, the arguments


FTP Log File Transfer Acknowledgement

Excelerator now supports positive acknowledgement of FTP log file transfers by renaming the temporary target file when the log transfer is complete.

To enable transfer acknowledgement, do the following:

  1. At the console prompt, enter the following command:

    set logpush useFileRename = yes

While the logs are being transferred, the file will have a typical Excelerator log file name with the extension .TMP. For example, during the transfer the log file might be named 01310015.TMP.

After the transfer is complete, Excelerator will rename the file to filename.LOG. Continuing with the example, the file would be renamed 01310015.LOG.


Per-Accelerator Cache Settings


Overview

Three of the parameters that previously applied only to the entire cache can now be set for each accelerator service. The options are:

Administers set these parameters for the entire cache using the command:

set cache parameter = yes|no

where parameter is one of the three parameters listed above.


What Has Changed

The three parameters are still settable for the entire cache and the default values still apply to Excelerator 2.3 SP2. What has changed is that these parameters are now optionally configurable for each accelerator service.


Using the Per-Accelerator Settings

You can set the parameters by doing the following:

  1. At the console prompt, enter the following command:

    set accelerator name parameter = default|yes|no

    where name is the name of the accelerator service you are configuring and parameter is one of the three parameters listed in the Overview.

NOTE:  You can set the parameters described in this section only at the console prompt. The parameters are not available in the browser-based management tool.

The effects of the available parameter settings on each accelerator service are summarized in Table 3.


Table 3. Per-Accelerator Cache Options

Option If setting = default If setting = yes If setting = no

filtercookies

The global cache setting for this parameter is used.

Cookies are not allowed to pass through the cache.

Cookies are allowed to pass through the cache.

objnocacheforquestionmark

The global cache setting for this parameter is used.

Objects containing a question mark (?) are not cached.

Objects containing a question mark (?) are cached.

objnocacheforcgi

The global cache setting for this parameter is used.

Objects containing CGI parameters are not cached.

Objects containing CGI parameters are cached.

To view the global cache settings, enter the following command at the console prompt:

get cache parameter

where parameter is the parameter you want to see.

To view the cache settings for an accelerator service , enter the following command at the console prompt:

get accelerator name parameter

where name is the name of the accelerator service and parameter is the parameter you want to see.