Re: wildcard(?) use inf wget 1.8

2002-02-18 Thread Hrvoje Niksic

cagri coltekin <[EMAIL PROTECTED]> writes:

> Apologies if this is a known issue. However, it seems that as of
> wget 1.8, the `?' char is treated as a separator in URLs. But this
> feature brakes the ftp downloads using wild-card `?'. It would be
> nice to disable this in url_parse() if url is not an https* url.

Thanks for the report.  The problem you described should be fixed by
this patch:

2002-02-19  Hrvoje Niksic  <[EMAIL PROTECTED]>

* url.c (url_parse): Don't treat '?' as query string separator
when parsing FTP URLs.

Index: src/url.c
===
RCS file: /pack/anoncvs/wget/src/url.c,v
retrieving revision 1.71
diff -u -r1.71 url.c
--- src/url.c   2002/01/26 20:43:17 1.71
+++ src/url.c   2002/02/19 05:07:24
@@ -802,6 +802,15 @@
   query_b = p;
   p = strpbrk_or_eos (p, "#");
   query_e = p;
+
+  /* Hack that allows users to use '?' (a wildcard character) in
+FTP URLs without it being interpreted as a query string
+delimiter.  */
+  if (scheme == SCHEME_FTP)
+   {
+ query_b = query_e = NULL;
+ path_e = p;
+   }
 }
   if (*p == '#')
 {



wildcard(?) use inf wget 1.8

2002-01-25 Thread cagri coltekin

Hi,

Apologies if this is a known issue. However, it seems that as of
wget 1.8, the `?' char is treated as a separator in URLs. But
this feature brakes the ftp downloads using wild-card `?'. It
would be nice to disable this in url_parse() if url is not an
https* url.

Regards.
-- 
cagri