> "without --disable-ipv6" mean?
It means when running the Configure script we did not specify the
--disable-ipv6 option.

Unfortunately, our test servers are internal and our customers are
accessing Microsoft Exchange with our products so that isn't an option
either. However, any hostname will do, but a good example is actually
to pass a non-existent IP address.

Here are a couple example, in both cases latest Curl run from the cmd
line. It was compiled and run on OS 10.2.8. Also, 192.168.1.234 does
not exist on our network.

With IPv6 Enabled:
"https://www.frontrange.edu/index.cfm" name lookup took: 1.964 seconds
"http://192.168.1.234" name lookup took: 22.632 seconds

With IPv6 Disabled:
"https://www.frontrange.edu/index.cfm" name lookup took: 0.003 seconds
"http://192.168.1.234" name lookup took: 0.001 seconds

On Monday, December 22, 2003, at 09:53 AM, Shantonu Sen wrote:

>
> On Dec 19, 2003, at 2:10 AM, Jacob Swed wrote:
>
>> The library version being used is 7.11.0-20031217. Compiled under OS
>> X 10.2.8.
>>
>> We have not investigated the why, but have determined that if
>> curl/libcurl is complied on OS X without the --disable-ipv6 option
>> performance is severely and noticeably degraded. curl/libcurl takes
>> an extremely long time resolving the host or host IP. Compiling with
>> the --disable-ipv6 option alleviates the delays entirely.
>> Incidentally, this occurs when run on vanilla installations of OS
>> 10.1, 10.2 and 10.3.
>
> Each one of those releases has had signifcantly different levels of
> support of both IPv6 in general, and IPv6 hostname resolution in
> specific. I don't think 10.1 shipped with any IPv6 support.
>
> What does "without --disable-ipv6" mean? Was IPv6 autodetected? I
> would not expect this on 10.1, for instance.
>
> Can you provide a test case (perhaps a specific hostname you were
> using and profiling information pointing at getaddrinfo if possible).
> If you can, I can take a look at this in the new year and see if Apple
> has existing problem reports relating to resolution speed and ask for
> improvements for the next release.
>
> Mac OS X should be hitting lookupd as a cache for all hostname
> resolution, so I would not expect a significant amount of network
> delay contributing to this issue after an initial lookup. Maybe that's
> not working.
>
> Shantonu
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills. Sign up for
> IBM's
> Free Linux Tutorials. Learn everything from the bash shell to sys
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Received on 2003-12-24