> > Updating httrack.com only used one connection.
> > For html and gif, ico.  Only if I deleted the .exe's
> > and updated did it use multiple connections.
> 
> Basically, link testing use the main connection.
> Background downloads may use more, but after all
> headers are processed (ie. for updates, you will not
> notice any parallel processing, because you only
> have "not modified" replies, and no data)

The only real reason for multiple connections is to divide the round trip plus
processing time by N.  On several sites I mirror, 3.32 takes over 7 seconds
per update request.  Sequential process isn't going to cut it.

> > 3.42-3 renamed all favicon.ico to .html:
> > > 10:31:36	Info: 	engine: transfer-status: link
> > updated: www.httrack.com/page/1/en/favicon.ico
> > %BASE%/web/favicon-4.html
> 
> This is actually an html page.
> 
> "www.httrack.com/page/1/en/favicon.ico" is a
> malformed link -- this is a website bug, obviously,
> but httrack successfully renamed it to html :p

It's not a website bug. link rel="shortcut icon" href="/favicon.ico" tells the
browser what icon to display to the left of the URL.  That the little black H
on gray.

> > 3.42-3 renamed all fade.gif to .html:
> > 10:32:15	Info: 	engine: transfer-status: link
> > updated: www.httrack.com/page/fade.gif
> 
> Same remark -- I'll have to cleanup image references
> within www.httrack.com

<http://www.httrack.com/page/7/en/index.html> contains both:
.tblRegular td    padding: 6px;  background-image: url(/fade.gif);  border:
2px solid #99c; 
and
table border="0" background="fade.gif" width="80%" cellpadding="10"

Both refer to an image.  They may be bogus on your site but on other sites
they refer to an image.  Httrack isn't processing the css correctly.