Support

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Web Proxy Caching > Ensuring cached object freshness > FTP object freshness
FTP object freshness
Help | Content Gateway | Version 7.7.3
FTP objects carry no time stamp or date information and remain fresh in the cache for the period of time you specify (from 15 minutes to 2 weeks), after which they are considered stale.
FTP objects can be requested from either an HTTP client (such as a browser) or an FTP client (such as WS_FTP). Content Gateway caches only the FTP objects requested from HTTP clients.
FTP objects requested by HTTP clients
You can set an absolute freshness limit for FTP objects requested by HTTP clients (FTP over HTTP objects).
 
* 
Note 
In addition to setting an absolute freshness limit for all FTP objects requested by HTTP clients, you can set freshness rules for specific FTP objects in the cache.config file (see cache.config).
1.
Navigate to Configure > Protocols > HTTP > Cacheability.
2.
In the FTP Document Lifetime area of the Freshness section, enter the amount of time that FTP objects requested by HTTP clients can remain fresh in the cache before being considered stale. The default value is 259200 seconds (3 days).
3.
Click Apply.
Print print article Email email article Font Size: A A

Search

Article Rating:

Do you have any additional feedback?    Email: close

Related Articles

Quick Links

Service Requests

How are we doing?

Provide us feedback on your experience with the Service Request portal.

provide feedback >

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Web Proxy Caching > Ensuring cached object freshness > FTP object freshness