Re: bug on wget
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hrvoje Niksic wrote: > Generally, if Wget considers a header to be in error (and hence > ignores it), the user probably needs to know about that. After all, > it could be the symptom of a Wget bug, or of an unimplemented > extension the server generates. In both cases I as a user would want > to know. Of course, Wget should continue to be lenient towards syntax > violations widely recognized by popular browsers. > > Note that I'm not arguing that Wget should warn in this particular > case. It is perfectly fine to not consider an empty `Set-Cookie' to > be a syntax error and to simply ignore it (and maybe only print a > warning in debug mode). That was my thought. I agree with both of your points above: if Wget's not handling something properly, I want to know about it; but at the same time, silently ignoring (erroneous) empty headers doesn't seem like a problem. - -- 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 iD8DBQFHRGqx7M8hyUobTrERCPwQAJ4wGFwPBqyoVDXjrOifNB/fVF1vtACbBnDU fnSx/Vj+S+DVnfRUbIz5HKU= =n4yr -END PGP SIGNATURE-
Re: bug on wget
Micah Cowan <[EMAIL PROTECTED]> writes: >> 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? That's what I meant. > I probably agree with that behavior... most people probably aren't > interested in being informed that a server breaks RFC 2616 mildly; Generally, if Wget considers a header to be in error (and hence ignores it), the user probably needs to know about that. After all, it could be the symptom of a Wget bug, or of an unimplemented extension the server generates. In both cases I as a user would want to know. Of course, Wget should continue to be lenient towards syntax violations widely recognized by popular browsers. Note that I'm not arguing that Wget should warn in this particular case. It is perfectly fine to not consider an empty `Set-Cookie' to be a syntax error and to simply ignore it (and maybe only print a warning in debug mode).
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-
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 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-
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
