Re: bug-wget still useful
P> I don't know why you say that. I see bug reports and discussion of fixes P> flowing through here on a fairly regular basis. All I know is my reports for the last few months didn't get the usual (any!) cheery replies. However, I saw them on Gmane, yes.
Re: bug-wget still useful
Dan Jacobson <[EMAIL PROTECTED]> writes: > Is it still useful to mail to [EMAIL PROTECTED] I don't think > anybody's home. Shall the address be closed? If you're referring to Mauro being busy, I don't see it as a reason to close the bug reporting address.
RE: bug-wget still useful
I don't know why you say that. I see bug reports and discussion of fixes flowing through here on a fairly regular basis. Mark Post -Original Message- From: Dan Jacobson [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 3:04 PM To: [EMAIL PROTECTED] Subject: bug-wget still useful Is it still useful to mail to [EMAIL PROTECTED] I don't think anybody's home. Shall the address be closed?
bug-wget still useful
Is it still useful to mail to [EMAIL PROTECTED] I don't think anybody's home. Shall the address be closed?
FTP size retrieval
With both 1.8.2 and 1.9.1b (Linux and Win32), fetching a new file via FTP does not retrieve the size, and hence does not display percentage and ETA information. It only queries the size when continuing a transfer. There appears to be no option to correct this behavior besides starting, cancelling, then restarting (with -c) the transfer.
Re: host header duplication in 1.9.1
John Andrea <[EMAIL PROTECTED]> writes: > I'm trying to connect to a virtual host even though the DNS does not > point to that host. I believe this should work if I specify the ip > address of the host and then use the Host: header within the > request. A test with telnet tells me that this works. > > However with wget 1.9.1 I see from the debug output that the Host: > header is duplicated in the HTTP request. Depending on your point of view, this is a bug or a missing feature in Wget 1.9.x. The CVS Wget has been fixed so it does what you (and many other people) would expect. Please see if it works for you; the download instructions are available at http://wget.sunsite.dk/.
Re: wget https://... behind proxy
[EMAIL PROTECTED] writes: > I found some problem to download page from https://... URL, when I > have connection only through proxy. For NON http protocols I use > CONNECT method, but wget seems to not use it and access directly > https URLS. For http:// URL wget downloads fine. > > Can you tell me, is it error in wget It's an error in Wget 1.9.x which has been fixed in current CVS. Please try using the CVS Wget and see if it works for you.
Re: what is a real download speed?
Roman Shiryaev <[EMAIL PROTECTED]> writes: > I usually download files using wget from one of ISP filesevers via > 8Mbps ADSL under linux. And wget always shows me that download speed > is no more than ~830 kbytes/sec. Now I guess that this is a transfer > speed of really useful data only (i.e. wget disregards some special > purpose network traffic). Yes, Wget shows the speed of the stream of bytes it receives from the system's TCP/IP stack. You can also think of it as the speed those bytes are saved to the file. > But one man who use the same ISP had told me that his "real" speed > is about 890 kb/sec under windows. I was surprised. Why? > > And only after watching incoming traffic by means of two network > monitors I've understood what is the real speed and what is > not. Monitors have shown me exactly the same what that man said > -- 890 kb/sec bandwidth. I believe that network monitors show the "raw" traffick, which includes TCP and IP headers, retransmitted packets, and possibly network traffick from programs other than Wget. Some also include upload transfer, which contains ACKs. I'm not sure if that can account for the additional 60 KB/s. I don't think user-level programs can really "utilize" the remaining traffick for their purposes, at least not without (re)implementing their own low-level protocols and breaking compatibility with existing servers.
wget https://... behind proxy
Hi, I found some problem to download page from https://... URL, when I have connection only through proxy. For NON http protocols I use CONNECT method, but wget seems to not use it and access directly https URLS. For http:// URL wget downloads fine. Can you tell me, is it error in wget or is there any option or cmdline param for this situation (to use proxy also for https)? If this is impossible for wget, can I have feature request to use proxy for https URLs too? Using CONNECT method. Thank you for answers. Bye. Wolf.
