On Thu, August 25, 2005 10:39 am, Christopher Sawtell said: > On Thu, 25 Aug 2005 10:24, Steve Holdoway wrote: >> On Thu, August 25, 2005 10:17 am, Christopher Sawtell said: >> >> If it's a bug, then how are you going to implement a standard file >> >> naming >> >> scheme across http and ftp? >> > >> > if there is a line such as this:- >> > Content-disposition: filename=laby_1.0.1.tar.gz >> > in the http headers then use the filename mentioned. >> > otherwise use the name of the file on server as is done currently. >> > >> > I have not yet examined the wget code so cannot comment on the exact >> > details. >> > >> > -- >> > CS >> >> Once again, how are you going to do this in ftp, where there are *no* >> headers? > Once again:- > "use the name of the file on server as is done currently." > >> I'm quite happy to lobby for an extra switch to enable this >> functionality >> for http gets, but not as a default. > Why, what is the problem? > > -- > CS > so you think it's acceptable behaviour for the web designer to create his directory hierarchy on your pc *without* you asking him to do so?
and it's ok to get foobar.exe when you ask for something else? wget's main function is to be used in scripting, as in Nick's original example ( see the first para of the intro on the gnu website ). How are you going to process any returned files when you a) don't know their name and b) don't know where they are? Things like that are problems. Big ones. Steve -- Windows: Where do you want to go today? MacOS: Where do you want to be tomorrow? Linux: Are you coming or what?
