01.01.2013 Views

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3<br />

Proxies and caching<br />

Common proxy settings<br />

ICAP Server<br />

Settings for the appliance when running as an ICAP server that modifies requests and responses in<br />

communication with ICAP clients<br />

Enable ICAP server — When selected, the appliance takes the role of an ICAP server<br />

ICAP Port Definition list — List of ports on the appliance that listen to requests from ICAP clients<br />

The following table describes the list entries. For information on maintaining a list of this type, see<br />

Inline lists.<br />

Table 3-11 ICAP Port Definition list<br />

Option Definition<br />

Listener address Local IP address of the appliance running as an ICAP server and port for requests from ICAP<br />

clients<br />

Send early 204<br />

responses<br />

Wait for complete<br />

ICAP request<br />

Maximal concurrent<br />

REQMOD connections<br />

Maximal concurrent<br />

RESPMOD<br />

connections<br />

<strong>Web</strong> Cache (setting)<br />

Setting for enabling the appliance web cache<br />

Enable cache — When selected, the web cache is enabled<br />

You can then use by an appropriate rule set to control reading from and writing to the cache.<br />

For more information, see <strong>Web</strong> caching.<br />

56 <strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong> <strong>7.1.5</strong> <strong>Product</strong> <strong>Guide</strong><br />

When selected, the appliance sends 204 responses early to clients before a request is fully<br />

transferred<br />

Note: Some clients do not support early 204 responses.<br />

(The main item does not appear in the table, but is visible in the Add and Edit windows. The<br />

following four elements in the table are related to it, specifying when the ICAP server should<br />

wait until a request is complete.)<br />

Waiting for the complete request can be necessary when clients are not capable of receiving<br />

parts of the filtered data in response while other parts of the request are still being sent to<br />

the server. The normal behavior for the ICAP server is to try to filter and send back data<br />

chunk by chunk to reduce latency time.<br />

• Never — When selected, the ICAP server never waits<br />

• Only for REQMOD requests — When selected, the ICAP server waits if the mode for<br />

modifying requests is used<br />

• Only for REQMOD requests — When selected, the ICAP server waits if the mode for<br />

modifying requests is used<br />

• Always — When selected, the ICAP server always waits<br />

Maximum number of connections the ICAP server can use simultaneously when modifying<br />

requests<br />

Maximum number of connections the ICAP server can use simultaneously when modifying<br />

responses<br />

Preview size Size (in bytes) of the portion of a request sent by a client to the ICAP server at the beginning<br />

of the communication<br />

The server asks for more data or lets the rest of the data pass through unmodified.<br />

Comment Plain-text comment on the ICAP server port

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!