Kazu Yamamoto wrote:
> Since I have experiences to modify IPv4 only programs, including FTP
> and HTTP, to IPv6-IPv4 one, I know this problem. Yes, some part of
> wget *would* remain protocol dependent.
Kazu, it's been said that a picture is worth a thousand words. Perhaps in
this case, a patch w
A happy new year!
> your page is not realy very usefull. First yes it describe how to code
> protocol independent but
> the big problem is it is ONLY valid for platforms with are full
> compatible with the newest functions.
I'm afraid that this is misunderstanding.
You can implement getaddrin
Thomas Lussnig <[EMAIL PROTECTED]> writes:
> your page is not realy very usefull. First yes it describe how to code
> protocol independent but
> the big problem is it is ONLY valid for platforms with are full
> compatible with the newest functions.
> In the first change of wget i also had reduced
> Hi, When I run this command from the DOS prompt:
> wget.exe --output-document=C:\F-Prot\FP-Def.zip
> --http-proxy=http://139.141.91.12:80/
> http://www.f-prot.com/cgi-bin/get_randomly?fp-def
> I get "unrecognized option '--http-proxy=http://139.141.91.12:80/'.
> Can U Please, e-mail me the rig
Hi,
When I run this command from the DOS prompt:
wget.exe --output-document=C:\F-Prot\FP-Def.zip --http-proxy=http://139.141.91.12:80/
http://www.f-prot.com/cgi-bin/get_randomly?fp-def
I get "unrecognized option '--http-proxy=http://139.141.91.12:80/'.
Can U Please, e-mail me the right command
