On Thu, May 2, 2013 at 12:32 PM, Tim Rühsen <tim.rueh...@gmx.de> wrote: > Am Donnerstag, 2. Mai 2013 schrieb Micah Cowan:
>> Ah, yeah that's a decent point. I like it, but then, we run into >> name-trusting problems along the lines of why --trust-server-names was >> introduced, if we just happily translate a hostname to its redirection >> (and in particular, begin accepting more pages with that unasked-for >> hostname). Obviously, using --trust-server-names solves the issue, but >> I'm not sure requiring that is any better, from a user experience, >> than adding -D -H. > > Right now, using --trust-server-names does not solve this issue (it just makes > wget trust the given filenames). > But we could use it to solve it. Right; what I meant was, we would have to force the user to use --trust-server-names in order to handle redirects in this way "safely", but then using this wouldn't be particularly easier for users than using -D -H is now. A little bit easier, since you don't have to figure out which hostnames to include with -D, but you still have to "know to do it", which i think was part of Darshit's complaint. > [BTW, -D doesn't solve the issue either. Try 'wget -d -r -D www.gnu.org > http://gnu.org. Not shure if -H -D www.gnu.org only spans to www.gnu.org and > not to any other domain.] You would want: -Dgnu.org -H. The -H is absolutely vital, or at least used to be (isn't implied by -D; possibly should be). Works for me (as did -Dwww.gnu.org, provided I gave the -H). -mjc
