Mechanics of updating

The way HTTrack renames and saves pages locally does not change the way HTTrack does updates, and does not influence the whole update process. The original remote hostname, filename and query strings are stored in the hts-cache file data, and HTTrack only uses that information to perform the update process.

The majority of the update process is dependant on the remote server, through two important processes:

• During the first project download, the server has to send a reliable way to tag the file/URL — such as a timestamp (current date+time) or, even better, a strong ETag header identifier (which can be an MD5 hash of the content—the "ultimate weapon" for handling updates). This information allows clients to identify the "freshness" of the data being sent.

- During an update, HTTrack requests the previously downloaded file, giving to the server the "hint" previously sent (timestamp, and/or ETag). It is the duty of the server to either respond with a "OK, file not modified" message (304), or using a "OOPS, you have to redownload this file" message (200).

Information sourced from forum http://forum.httrack.com/readmsg/3062/index.html