Showing revision 1

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 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