"William A. Rowe, Jr." <[EMAIL PROTECTED]> writes:
> Yes, however Win32 would start with IPv6 with the
>
> Listen 80
>
> directive last week. Something changed this week that the default
> IP [0::0] no longer works correctly. Named IPs were giving me trouble
> all along.
I know what you mean
At 06:49 AM 10/27/2002, Jeff Trawick wrote:
>I don't see how any of this commit affects that path...
It may not. There -are- problems with the IPV6 port on Win32, yet
and still...
>didn't you say almost exactly the same thing after commiting something
>to turn on IPv6 for Win32 about a week ago
"William A. Rowe, Jr." <[EMAIL PROTECTED]> writes:
> FWIW, somehow this patch breaks Win32 with APR_HAVE_IPV6.
>
> The Apache service named reported the following error:
> >>> [Sat Oct 26 22:45:29 2002] [crit] (OS 11001)No such host is known. :
>alloc_listener: failed to set up sockaddr for ::
FWIW, somehow this patch breaks Win32 with APR_HAVE_IPV6.
The Apache service named reported the following error:
>>> [Sat Oct 26 22:45:29 2002] [crit] (OS 11001)No such host is known. :
>alloc_listener: failed to set up sockaddr for :: .
No time to debug now... a dozen overdue assignments.
