Re: frames

2005-04-18 Thread Alan Thomas
It doesn`t seem to download the file when I use the debug option.  It just quickly says "finished."  Hrvoje Niksic <[EMAIL PROTECTED]> wrote: Alan Thomas <[EMAIL PROTECTED]>writes:> The log file looks like:> > 17:54:41 URL:https://123.456.89.01/blabla.nsf/HOBART?opeNFRAMESET> [565/565] -> "123

wget does not follow urls containing wildcards

2005-04-18 Thread peter pilsl
when doing recursive downloading on a page that contains * in its url, wget gives me the warning, that * are not allowed in the url and does not follow the documents: Warning: wildcards not supported in HTTP. Point is, that the documents are only reachable via * in the url. The page works on all co

Re: wget spans hosts when it shouldn't and fails to retrieve dirs starting with a dot...

2005-04-18 Thread Hrvoje Niksic
Jörn Nettingsmeier <[EMAIL PROTECTED]> writes: > the same parser code might also work for urls in javascript. as it > is now, mouse-over effects with overlay images don't work, because > the second file is not retrieved. if we can come up with a good > heuristics to guess urls, it should work in b

Re: wget spans hosts when it shouldn't and fails to retrieve dirs starting with a dot...

2005-04-18 Thread Jörn Nettingsmeier
Hrvoje Niksic wrote: Jörn Nettingsmeier <[EMAIL PROTECTED]> writes: wget does not parse css stylesheets and consequently does not retrieve url() references, which leads to missing background graphics on some sites. this feature request has not been commented on yet. do think it might be useful ? I

Re: wget spans hosts when it shouldn't and fails to retrieve dirs starting with a dot...

2005-04-18 Thread Hrvoje Niksic
Jörn Nettingsmeier <[EMAIL PROTECTED]> writes: >wget does not parse css stylesheets and consequently does not >retrieve url() references, which leads to missing background >graphics on some sites. >>> >>>this feature request has not been commented on yet. do think it >>>might be useful

Random non-base64 chars in base64

2005-04-18 Thread Hrvoje Niksic
Quoting rfc2047, section 6.8: All line breaks or other characters not found in Table 1 [the base64 alphabet] must be ignored by decoding software. I would take that to mean that upon encountering, for example, the character "<" in the base64 stream, Wget should ignore it and proceed to the

Re: wget spans hosts when it shouldn't and fails to retrieve dirs starting with a dot...

2005-04-18 Thread Jörn Nettingsmeier
Hrvoje Niksic wrote: Jörn Nettingsmeier <[EMAIL PROTECTED]> writes: [3] wget does not parse css stylesheets and consequently does not retrieve url() references, which leads to missing background graphics on some sites. this feature request has not been commented on yet. do think it might be useful

Re: wget spans hosts when it shouldn't and fails to retrieve dirs starting with a dot...

2005-04-18 Thread Hrvoje Niksic
Jörn Nettingsmeier <[EMAIL PROTECTED]> writes: >>> [3] >>> >>> wget does not parse css stylesheets and consequently does not >>> retrieve url() references, which leads to missing background >>> graphics on some sites. > > this feature request has not been commented on yet. do think it > might be u

Re: wget spans hosts when it shouldn't and fails to retrieve dirs starting with a dot...

2005-04-18 Thread Jörn Nettingsmeier
hi wgetters ! a while ago, i wrote: [1] wget spans hosts when it shouldn't: it looks like this behaviour is by design, but it should be documented. [2] wget seems to choke on directories that start with a dot. i guess it thinks they are references to external pages and does not download links con