You can check the headers by opening up chrome s developer tools On 26 Jun 2013 13:44, "David Haslam" <[email protected]> wrote:
> I'm not consciously using a proxy to access Michael's ftp directory, but > this > description might be a possible explanation somewhere along the connection. > > > *FTP caching* > > When the proxy is configured to cache requests, it can cache FTP file > requests as well as HTTP file requests. However, because FTP files do not > contain the same type of header information as HTTP files, expiration dates > for cached FTP files are calculated differently than for other cached > files. > > When a request is made to the FTP server to retrieve a file, the proxy > first > sends to the FTP server a LIST request for the file to obtain FTP directory > information about the file. If the FTP server responds to the LIST request > with a positive completion reply and the directory information for the > file, > the proxy creates an HTTP Last-Modified header with the date parsed from > the > FTP directory information. The caching function of the proxy then uses this > Last-Modified header, together with the value set in the > CacheLastModifiedFactor directive in the configuration file, to determine > the length of time that the FTP file remains in the cache before expiring. > > David > > > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/eBible-org-OSIS-files-regenerated-again-tp4652644p4652646.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: [email protected] > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page >
_______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
