From 9b5c6cf86ed8dbf749bc2e401d4f87d340b6413d Mon Sep 17 00:00:00 2001 From: Xavier Roche Date: Wed, 15 Oct 2014 19:17:29 +0000 Subject: Fixed webhttrack incompatibility with Chrome * closes:#53 Also fixed HTML-escaping issues inside webhttrack Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones. --- html/server/help.html | 81 ++++----------------------------------------------- 1 file changed, 5 insertions(+), 76 deletions(-) (limited to 'html/server/help.html') diff --git a/html/server/help.html b/html/server/help.html index 19decdb..5b55586 100755 --- a/html/server/help.html +++ b/html/server/help.html @@ -6,79 +6,8 @@ '${projname}' - HTTrack Website Copier - + +