may tend towards the top). Not all of these represent user-visible
changes.
-* -p should probably go "_two_ more hops" on <FRAMESET> pages.
+* Be careful not to lose username/password information given for the
+ URL on the command line.
+
+* Support FWTK firewalls. It should work like this: if ftp_proxy is
+ set to an ftp URL, Wget should assume the use of an FWTK firewall.
+ It should connect to the proxy URL, log in as username@target-site,
+ and continue as usual.
-* Only normal link-following recursion should respect -np. Page-requisite
- recursion should not. When -np -p is specified, Wget should still retrieve
- requisite images and such on the server, even if they aren't in that directory
- or a subdirectory of it. Likewise, -H -np -p should retrieve requisite files
- from other hosts.
+* -p should probably go "_two_ more hops" on <FRAMESET> pages.
* Add a --range parameter allowing you to explicitly specify a range of bytes to
get from a file over HTTP (FTP only supports ranges ending at the end of the
* Try to devise a scheme so that, when password is unknown, Wget asks
the user for one.
-* Limit the number of successive redirection to max. 20 or so.
-
* If -c used with -N, check to make sure a file hasn't changed on the server
before "continuing" to download it (preventing a bogus hybrid file).
* Make -K compare X.orig to X and move the former on top of the latter if
they're the same, rather than leaving identical .orig files laying around.
-* If CGI output is saved to a file, e.g. cow.cgi?param, -k needs to change the
- '?' to a "%3F" in links to that file to avoid passing part of the filename as
- a parameter.
-
-* Make `-k' convert <base href=...> too.
-
* Make `-k' check for files that were downloaded in the past and convert links
to them in newly-downloaded documents.