Re: Can't add ampersand to url I want to get
Single quotes will work when a URL includes a dollar sign. Double quotes won't. On Nov 5, 2007 12:07 PM, Micah Cowan [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alles, Kris wrote: I tried wrapping the url with double quotes instead of single quotes and it works. Please disregard previous message. Both single and double quotes should work in typical Unix shells. Unless, of course, the quoted text contains a quote (which URIs usually shouldn't). - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHL3f87M8hyUobTrERCE29AJ0cYTbE+ukuyO2QwlLmpL8Jl8VJXwCeMAfD qToM3B1IsbY6BCjtRD94JBU= =wkDU -END PGP SIGNATURE- -- Best Regards. Please keep in touch.
bug on wget
Hi, I got a bug on wget when executing: wget -a log -x -O search/search-1.html --verbose --wait 3 --limit-rate=20K --tries=3 http://www.nepremicnine.net/nepremicninske_agencije.html?id_regije=1 Segmentation fault (core dumped) I created directory search. The above creates a file search/search-1.html zero-sized. Logfile log: Resolviendo www.nepremicnine.net... 212.103.144.204 Conectando a www.nepremicnine.net|212.103.144.204|:80... conectado. Petición HTTP enviada, esperando respuesta... 200 OK --18:18:28-- http://www.nepremicnine.net/nepremicninske_agencije.html?id_regije=1 = `search/search-1.html' (I hope you understand the Spanish above. If not, labels are the usual: resolving, connecting, HTTP petition sent, waiting for request) It happens the same when varying the parameter on the url id_regije, just in case it helps. I'm using Intel CoreDuo E6300, plenty of disk/mem space. ubuntu 7.10 Should you need any further information don't hesitate to contact. Regards Diego
Error with --recursive = zero exit status?
GNU Wget 1.10.2, and it's more an inconsitency than a bug. Basically, if something goes wrong with the network connection while downloading recursively, wget will time-out as expected, but without reporting any kind of an error. No non-zero exit status, at least. So when I put this in a script; while : do wget -c -r -T 33 -np \ 'http://www.tux.org/pub/people/kent-robotti/looplinux/rip/docs/' \ break || \ sleep 11 done # End This is what happens if the connection is dropped, or if there was none to begin with; --09:29:11-- http://www.tux.org/pub/people/kent-robotti/looplinux/rip/docs/ = `www.tux.org/pub/people/kent-robotti/looplinux/rip/docs/index.html' Resolving www.tux.org... failed: Temporary failure in name resolution. FINISHED --09:29:11-- Downloaded: 0 bytes in 0 files Then the script exits, believing the download finished without any trouble. I think you should be able to replicate this easily, as long as you're offline when you try it. Thanks, Patrick. -- The error of youth is to believe that intelligence is a substitute for experience, while the error of age is to believe experience is a substitute for intelligence. -- Lyman Bryson
Re: Error with --recursive = zero exit status?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Micah Cowan wrote: Patrick wrote: GNU Wget 1.10.2, and it's more an inconsitency than a bug. I definitely consider it a bug. Basically, if something goes wrong with the network connection while downloading recursively, wget will time-out as expected, but without reporting any kind of an error. No non-zero exit status, at least. This appears to still be the case. I consider this an important bug. ...but probably not a show-stopper. It _should_ be easy enough to fix, so hopefully I'll have it in in time for release (and of course, if someone wants to submit a patch I'll be grateful); but it's possible it'd have to wait until 1.12. :\ On second thought, while it's easy to say that this should happen when only one URL has been tried, it's really difficult to say what should happen when some URLs have succeeded, and some have failed. This is really part of the whole how should Wget handle error conditions, particularly for recursions thing, which needs some more thorough discussion. So, looks like I'll probably wait on this until 1.12. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHQy5a7M8hyUobTrERCGUgAJ0TFhJcJp1wtSbpBPAaTEouOheOUACfRtQ7 NvQMqkF8RU0U/Rwtz758UgU= =mqy7 -END PGP SIGNATURE-
Re: Error with --recursive = zero exit status?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Patrick wrote: GNU Wget 1.10.2, and it's more an inconsitency than a bug. I definitely consider it a bug. Basically, if something goes wrong with the network connection while downloading recursively, wget will time-out as expected, but without reporting any kind of an error. No non-zero exit status, at least. So when I put this in a script; while : do wget -c -r -T 33 -np \ 'http://www.tux.org/pub/people/kent-robotti/looplinux/rip/docs/' \ break || \ sleep 11 done # End This is what happens if the connection is dropped, or if there was none to begin with; --09:29:11-- http://www.tux.org/pub/people/kent-robotti/looplinux/rip/docs/ = `www.tux.org/pub/people/kent-robotti/looplinux/rip/docs/index.html' Resolving www.tux.org... failed: Temporary failure in name resolution. FINISHED --09:29:11-- Downloaded: 0 bytes in 0 files Then the script exits, believing the download finished without any trouble. This appears to still be the case. I consider this an important bug. ...but probably not a show-stopper. It _should_ be easy enough to fix, so hopefully I'll have it in in time for release (and of course, if someone wants to submit a patch I'll be grateful); but it's possible it'd have to wait until 1.12. :\ - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHQyvq7M8hyUobTrERCN2nAJ99MGd59A+nmLI2Xe+sAwsEcSgdVACfYNXn riefDalraLmUigxwIwXtGpw= =0eiB -END PGP SIGNATURE-
Re: bug on wget
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Diego Campo wrote: Hi, I got a bug on wget when executing: wget -a log -x -O search/search-1.html --verbose --wait 3 --limit-rate=20K --tries=3 http://www.nepremicnine.net/nepremicninske_agencije.html?id_regije=1 Segmentation fault (core dumped) Hi Diego, I was able to reproduce the problem above in the release version of Wget; however, it appears to be working fine in the current development version of Wget, which is expected to release soon as version 1.11.* * Unfortunately, it has been expected to release soon for a few months now; we got hung up with some legal/licensing issues that are yet to be resolved. It will almost certainly be released in the next few weeks, though. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHQypR7M8hyUobTrERCF99AJ4w790h4juXzPwO+csBbSY3KcLOXACdGYgO Kf4Oawgfjx6WOEzYwkQ47mw= =8gL2 -END PGP SIGNATURE-
Re: How to change the name of the output file
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Andra Isan wrote: Hi, When I download a file, I would like to change the output file, usually the name is long and I would like to change that name, How can I do so? Andra Depending on your needs, -O filename might fit the bill. Be advised, though, that -O doesn't simply mean make the name of the downloaded result `filename'; it means act as if you're redirecting output to a file named `filename'. In particular, this means that such things as timestamping, and multiple URLs, may not work as you expect. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHQzel7M8hyUobTrERCE6vAJ9bMNqSgxviNSVs8LEoOsPuQPCT2ACghnan 9FGF94GenJIfQtGHXvKgfYw= =jQE6 -END PGP SIGNATURE-
How to change the name of the output file
Hi, When I download a file, I would like to change the output file, usually the name is long and I would like to change that name, How can I do so? Andra - Get easy, one-click access to your favorites. Make Yahoo! your homepage.
Wget Release Status
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I haven't heard back from Brett Smith very recently, and am waiting to see what the progress is on the licensing situation. However, I just received word back from RMS that a release under GPLv2+ (the license used in previous releases) will be acceptable if resolution of the GPLv3+ licensing exceptions continues to meet with delays. We're waiting to hear further information from Brett Smith to get an idea of how close to the light at the end of the tunnel we might be on that. In the meantime, there are a few bugs that have been reported against 1.11 that I would want to resolve before release, but probably none of them are absolute show-stoppers (though I'd really like to at least get the --no-parents bug squared away: https://savannah.gnu.org/bugs/index.php?21530). I haven't had time to dig into them lately (been pretty busy); but I expect them to be fairly minor fixes, and hope to get them knocked out in the next week or so. At any rate, we should be looking at a release (finally!) at around the turn of the month. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHQznq7M8hyUobTrERCK1XAJ0STH3lTJycl01YYPjCE9lD7WwudQCfZfzv DpClSqtTPo2BVdVmD9i2KJA= =4mUf -END PGP SIGNATURE-
Re: bug on wget
Micah Cowan [EMAIL PROTECTED] writes: I was able to reproduce the problem above in the release version of Wget; however, it appears to be working fine in the current development version of Wget, which is expected to release soon as version 1.11.* I think the old Wget crashed on empty Set-Cookie headers. That got fixed when I converted the Set-Cookie parser to use extract_param. The new Wget flags empty Set-Cookie as a syntax error (but only displays it in -d mode; possibly a bug).
Re: bug on wget
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hrvoje Niksic wrote: Micah Cowan [EMAIL PROTECTED] writes: I was able to reproduce the problem above in the release version of Wget; however, it appears to be working fine in the current development version of Wget, which is expected to release soon as version 1.11.* I think the old Wget crashed on empty Set-Cookie headers. That got fixed when I converted the Set-Cookie parser to use extract_param. The new Wget flags empty Set-Cookie as a syntax error (but only displays it in -d mode; possibly a bug). I'm not clear on exactly what's possibly a bug: do you mean the fact that Wget only calls attention to it in -d mode? I probably agree with that behavior... most people probably aren't interested in being informed that a server breaks RFC 2616 mildly; especially if it's not apt to affect the results. Unless of course the user was expecting that the user send a real cookie, but I'm guessing that this only happens when the server doesn't have one to send (or something). But a user in that situation should be using -d (or at least - -S) to find out what the server is sending. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHQ3N97M8hyUobTrERCCpFAJ9RHcdJ8X4UWpEQIhz+khDWc8MOJwCfZANU vr2lCTLP04R/PP/cBf7sIpE= =6csr -END PGP SIGNATURE-
