ipv6 patch

2003-11-19 Thread Herold Heiko
-- -- PREVINET S.p.A. www.previnet.it -- Heiko Herold [EMAIL PROTECTED] -- +39-041-5907073 ph -- +39-041-5907472 fax 20031119.diff Description: Binary data

Re: ipv6 patch

2003-11-19 Thread Hrvoje Niksic
Herold Heiko [EMAIL PROTECTED] writes: Attached a little patch needed for current cvs in order to compile on windows nt 4 (any system without IPV6 really). Thanks. Note that the function isn't even called when IPv6 is unavailable, so you can feel free to wrap the entire function in #ifdef

Re: ipv6 patch

2003-11-19 Thread Gisle Vanem
Herold Heiko [EMAIL PROTECTED] said: Attached a little patch needed for current cvs in order to compile on windows nt 4 (any system without IPV6 really). FYI, Wget/IPv6 on Windows do work somewhat; getaddrinfo() is able to resolve a host to it's IPv6 address(es). But getnameinfo() isn't able

Re: ipv6 patch

2003-11-19 Thread Hrvoje Niksic
Gisle Vanem [EMAIL PROTECTED] writes: Due to lack of inet_ntop() on Windows, I used this instead: struct sockaddr_in6 addr6; addr6.sin6_family = AF_INET6; memcpy (addr6.sin6_addr, address, sizeof(addr6.sin6_addr)); if (getnameinfo ((const struct sockaddr*)addr6, sizeof(addr6),

Re: ipv6 patch

2003-11-19 Thread Gisle Vanem
but Wget doesn't check return value of inet_ntop(). Hint hint. I wasn't aware that inet_ntop could really fail. Why did getaddrinfo return the address if I can't print it? getaddrinfo() on Win-XP seems to be a thin wrapper over the DNS client which resolves records fine. But

Re: ipv6 patch

2003-11-19 Thread Hrvoje Niksic
Gisle Vanem [EMAIL PROTECTED] writes: but Wget doesn't check return value of inet_ntop(). Hint hint. I wasn't aware that inet_ntop could really fail. Why did getaddrinfo return the address if I can't print it? getaddrinfo() on Win-XP seems to be a thin wrapper over the DNS client which

recv and the MSG_PEEK flag

2003-11-19 Thread Hrvoje Niksic
Does anyone know whether the MSG_PEEK flag can be relied upon? I'd like to use peeking to get rid of the ad hoc rbuf layer used in Wget since time immemorial. Peeking would require additional work under SSL, but I think I know how to make it work. But I'm more worried about TCP/IP stacks that

problem with LF/CR etc.

2003-11-19 Thread Peter GILMAN
hello. i have run into a problem while using wget: when viewing a web page with html like this: a href=images/IMG_01 .jpgimg src=images/tnIMG_01 .jpg/a browsers (i tested with mozilla and IE) can handle the line breaks in the urls (presumably stripping them out), but wget chokes on

RE: problem with LF/CR etc.

2003-11-19 Thread Post, Mark K
That is _really_ ugly, and perhaps immoral. Make it an option, if you must. Certainly don't make it the default behavior. Shudder Mark Post -Original Message- From: Hrvoje Niksic [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 4:59 PM To: Peter GILMAN Cc: [EMAIL