Alain Guibert [EMAIL PROTECTED] writes:
This old system does HAVE_WORKING_FNMATCH_H (and thus
SYSTEM_FNMATCH). When #undefining SYSTEM_FNMATCH, the test still
fails at the very same line. And then it also fails on modern
systems. I guess this points at the embedded src/cmpt.c:fnmatch()
wget-1.11.1 (and 1.10/1.10.1) don't handle the .listing file properly when -c
is used.
It just appends to that file instead of replacing it which means that wget
tries to download each
file twice when you run the same command twice. Have a look at this log:
wget -m -nd -c
Hi Hrvoje Niksic / Micah Cowan
I am having strange problem with wget 1.11 version. While accessing a
webserver which is running on Verisign issued Trial certificates, wget
1.11 gives following error even though that certificate is valid.
[EMAIL PROTECTED]:/root $ wget
On Wednesday, April 2, 2008 at 23:09:52 +0200, Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
It's hard for me to imagine an fnmatch that ignores FNM_PATHNAME
The libc 5.4.33 fnmatch() supports FNM_PATHNAME, and there is code
apparently intending to return FNM_NOMATCH on a slash.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
The log shows that:
1. Wget still doesn't wait for the Proxy to ask for authentication,
before sending Proxy-Authorization headers with its first request.
2. Apparently, when going through a proxy, Wget now correctly waits
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amit Patel wrote:
Hi Hrvoje Niksic / Micah Cowan
I am having strange problem with wget 1.11 version. While accessing a
webserver which is running on Verisign issued Trial certificates, wget
1.11 gives following error even though that
On Thursday, April 3, 2008 at 11:08:27 +0200, Hrvoje Niksic wrote:
Well, it would point to a problem with both the fnmatch replacement
and the older system fnmatch. Our fnmatch (coming from an old
release of Bash
The fnmatch()es in libc 5.4.33 and in Wget are twins. They differ on
some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alain Guibert wrote:
The for loop intended to eat several characters from the string also
advances the pattern pointer. This one reaches the end of the pattern,
and points to a NUL. It is not a '*' anymore, so the loop exits
prematurely. Just
