Re: feature request: --second-guess-the-dns

2003-11-18 Thread Tony Lewis
Hrvoje Niksic wrote: Have you seen the rest of the discussion? Would it do for you if Wget correctly handled something like: wget --header='Host: jidanni.org' http://216.46.192.85/ I think that is an elegant solution. Tony

RE: feature request: --second-guess-the-dns

2003-11-17 Thread Herold Heiko
From: Hrvoje Niksic [mailto:[EMAIL PROTECTED] Dan Jacobson [EMAIL PROTECTED] writes: But I want a --second-guess-the-dns=ADDRESS Aside from `--second-guess-the-dns' being an awful name (sorry), what is the usage scenario for this kind of option? I.e. why would anyone want to

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Hrvoje Niksic
Come to think of it, I've had need for this before; the switch makes at least as much sense as `--bind-address', which I've never needed myself. Maybe `--connect-address' would be a good name for the option? It would nicely parallel `--bind-address'. Are there any takers to implement it?

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Hrvoje Niksic
Herold Heiko [EMAIL PROTECTED] writes: From: Hrvoje Niksic [mailto:[EMAIL PROTECTED] Maybe `--connect-address' would be a good name for the option? It would nicely parallel `--bind-address'. I was wondering if it should be possibile to pass more than one name to address change (for

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Daniel Stenberg
On Mon, 17 Nov 2003, Hrvoje Niksic wrote: Come to think of it, I've had need for this before; the switch makes at least as much sense as `--bind-address', which I've never needed myself. Maybe `--connect-address' would be a good name for the option? It would nicely parallel

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Maciej W. Rozycki
On Sun, 16 Nov 2003, Hrvoje Niksic wrote: You can do this now: wget http://216.46.192.85/ Using DNS is just a convenience after all, not a requirement. Unfortunately, widespread use of name-based virtual hosting made it a requirement in practice. ISP's typically host a bunch of web

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Hrvoje Niksic
Maciej W. Rozycki [EMAIL PROTECTED] writes: Hmm, couldn't --header Host: hostname work? I think it could, but now wget appends it instead of replacing its own generated one... It's not very hard to fix `--header' to replace Wget-generated values. Is there consensus that this is a good

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Dan Jacobson
By the way, I did edit /etc/hosts to do one experiment http://groups.google.com/groups?threadm=vrf7007pbg2136%40corp.supernews.com i.e. [EMAIL PROTECTED] to test an IP/name combination, without waiting for DNS's to update. Good thing I was root so I could do it. I sure hope that when one sees

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Dan Jacobson
P == Post, Mark K [EMAIL PROTECTED] writes: P You can do this now: P wget http://216.46.192.85/ P Using DNS is just a convenience after all, not a requirement. but then one doesn't get the HTTP Host field set to what he wants.

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Hrvoje Niksic
Dan Jacobson [EMAIL PROTECTED] writes: I sure hope that when one sees Connecting to jidanni.org[216.46.192.85]:80... connected. that there is no interference along the way, that that IP is really where we are going, to wget's best ability. I can guarantee that much -- the entire point of

Re: feature request: --second-guess-the-dns

2003-11-17 Thread Dan Jacobson
H It's not very hard to fix `--header' to replace Wget-generated H values. H Is there consensus that this is a good replacement for H `--connect-address'? I don't want to tamper with headers. I want to be able to do experiments leaving all variables alone except for IP address. Thus

Re: feature request: --second-guess-the-dns

2003-11-16 Thread Hrvoje Niksic
Dan Jacobson [EMAIL PROTECTED] writes: But I want a --second-guess-the-dns=ADDRESS Aside from `--second-guess-the-dns' being an awful name (sorry), what is the usage scenario for this kind of option? I.e. why would anyone want to use it? Perhaps the user should do all this in the

Re: feature request: --second-guess-the-dns

2003-11-16 Thread Hrvoje Niksic
Post, Mark K [EMAIL PROTECTED] writes: You can do this now: wget http://216.46.192.85/ Using DNS is just a convenience after all, not a requirement. Unfortunately, widespread use of name-based virtual hosting made it a requirement in practice. ISP's typically host a bunch of web sites on

feature request: --second-guess-the-dns

2003-11-15 Thread Dan Jacobson
I see there is --bind-address=ADDRESS When making client TCP/IP connections, bind() to ADDRESS on the local machine. ADDRESS may be specified as a hostname or IP address. This option can be useful if your machine is bound to multiple IPs. But I want a

RE: feature request: --second-guess-the-dns

2003-11-15 Thread Post, Mark K
You can do this now: wget http://216.46.192.85/ Using DNS is just a convenience after all, not a requirement. Mark Post -Original Message- From: Dan Jacobson [mailto:[EMAIL PROTECTED] Sent: Saturday, November 15, 2003 4:00 PM To: [EMAIL PROTECTED] Subject: feature request: --second