Hi Taras, Thanks for your interest in Wget.
On 10/31, taras.malivanc...@totaldefense.com wrote:
This might be an interesting option to consider. I'm not aware of any option to limit downloads based on a single file's size. However, you must remember that not all servers send a Content-Length header. In such scenarios, Wget *must* download the file before it realizes its actual size. In such a case, what would be the expected outcome? Should Wget delete the larger file? Or retain it?Hi all,I use wget, I think such features will be useful.Are there objections against the below, or something is already implemented and I did not find?1) Maximal size of downloaded file (not all the batch) : do not download if value in header present and stop and delete otherwise if it is too big. I implemented it in my internal version. This prevents downloading huge files when downloading from list and the process is not controlled manually.
2) Rename output to file001...bin if the URL produces junk name (now unable to download).Additional option - for any non-7bit chars.Could you please explain this issue further? What kind of junk name causes Wget to refuse downloading? A test case would be the best way to demonstrate this.
Look at the manual page for Wget, under the --output-document section. It explains why -N and -O do not fit well together.3) -N should work with - O ,also for bad output names without -O.
-- Thanking You, Darshit Shah
pgp6KbLOgPzch.pgp
Description: PGP signature
