Re: downloading https site with a username and password
It's hard to be sure without seeing the actual Web page, but if you're hittng a Submit button, then you're probably filling out a form, and so you probably need to specify the form data (such as the username and password) using the --post-data or --post-file options. Steven M. Schweda [EMAIL PROTECTED] 382 South Warwick Street(+1) 651-699-9818 Saint Paul MN 55105-2547
RE: wget www.openbc.com post-data/cookie problem
Erich Steinboeck wrote: > Is there a way to trace the browser traffic and compare > that to the wget traffic, to see where they differ. You can use a web proxy. I like Achilles: http://www.mavensecurity.com/achilles Tony
Problem with read timeout and retry option
Hi ! I need wget to quit trying to download a file if it encounters any problem more than 2 times. So I specified a connection timeout and a dns timeout and retry count as 2. This works fine. If connection cannot be established for two tries, wget exits. Now the problem is, if the network connectivity is lost in between. Here the read timeout comes into picture. If there is not network activity for "read timeout", then wget starts the file download all over again. Retry does not have any effect here. Each time read timeout occurs, wget tries for a new download, and again read timeout happens. When this happens, it seems as if wget is stuck, it never exits. I want this also to happen only 'n' times. How can I configure this? Would be glad if anyone could help me out. Thanks in advance. Cheers Lilian.- Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.
Re: wget www.openbc.com post-data/cookie problem
as you can see the problem is with the web server, that does not return a cookie (by means of the Set-Cookie header) to wget. Yes, that's exactly the problem. Logging on with a standard browser *does* return a cookie and successfully logs you on. Trying the same with wget, the server does *not* return a cookie, but instead returns message "Your browser cookies couldn't be recognized." in the downloaded HTML. Two questions: 1. Is there a way to trace the browser traffic and compare that to the wget traffic, to see where they differ. 2. Do you have a working wget example for any publicly accessible server, which uses POST and successfully returns a cookie? Thanks!
Re: WGET RFE: Minimum transfer speed
Jeff Dickey <[EMAIL PROTECTED]> writes: > It would be very nice if there were a complement to the --limit-rate > parameter to specify a minimum allowable transfer rate, such as -M > or --minimum-rate; this would abort a transfer and cause wget to > terminate with a nonzero exit code when the transfer rate dropped > below a user-specified minimum speed. What would this be useful for, exactly? Are you saying that your provider is intentionally capping your bandwidth? If so, how would terminating the download help?
WGET RFE: Minimum transfer speed
It would be very nice if there were a complement to the --limit-rate parameter to specify a minimum allowable transfer rate, such as -M or --minimum-rate; this would abort a transfer and cause wget to terminate with a nonzero exit code when the transfer rate dropped below a user-specified minimum speed. For those of us still dealing with Soviet-class monopoly telecom providers (I'm in Malaysia), it would ssave a certain amount of frustration. Please cc any replies or pointers to me directly, as I am not (yet) a subscriber to the list. Many thanks for your time. Sincerely, Jeff Dickey -- Jeff Dickey [EMAIL PROTECTED] Seven Sigma Software and Services Phone/SMS: +6012 373 8513 FOAF: http://www.seven-sigma.com/foaf.rdf Yahoo! IM: jeff_dickey ICQ: 8053918 Tencent QQ: 30302349 -- If you can't reach me by any of these, one of us may be permanently offline -- I use and recommend GNU Privacy Guard to authenticate and secure email messages! Public key: Download here - Key ID 27F20D92 Fingerprint: B6FB B5DB 9FB5 2ADE B4B3 AF6C 3467 5D64 27F2 0D92 signature.asc Description: OpenPGP digital signature
