I'd like to stir up again an old (unresolved) problem regarding the directory structure used to save files. Currently if we have a host.site.domain with several services (say, http, https and ftp) and run one or multiple downloads we could have collision due to files with the same name downloaded with different protocols.
Think a http://www.some.site/index.html with links to https://www.some.site.index.html (and why not, even to ftp://www.some.site/index.html), all three files different. Currently wget will try to save these files all to ./www.some.site/index.html (usually). Solution 1: have a switch like --use-protocol-dir = [no|most|all] "no" would be the current state: ./www.some.site/index.html ./www.some.site/index.html ./www.some.site/index.html "all" would be: always add a directory level for the protocol: ./http/www.some.site/index.html ./https/www.some.site/index.html ./ftp/www.some.site/index.html "most" would be mixed, http (used most) without, other protocols with: ./www.some.site/index.html ./https/www.some.site/index.html ./ftp/www.some.site/index.html) However I think the third solution would be ugly and confusing. The second would solve the problem, but most people won't like the extra directory, so probably the default should still be "no" Solution 2 would be not adding the protocol as an extra directory structure, but adding it in the directory name. Really ugly and confusing however it is implmented (for example ./httpss.domain.org/ is a http://ss.domain.org or a https://s.domain.org ?) but another possibility. This whole thing has been already discussed time ago, in the end the behavior was unchanged. I still think an option would be correct. Heiko -- -- PREVINET S.p.A. www.previnet.it -- Heiko Herold [EMAIL PROTECTED] -- +39-041-5907073 ph -- +39-041-5907472 fax
