On 19-Mar-07, at 8:31 PM, Phil Pennock wrote:
So Safari doesn't use IPv6 for http: _unless_ you do "something
fancy",
with the cut-over being somewhere along the authentication line (does
Basic cut it? I don't know).
My (admittedly limited) tasting tends to imply that this is not true.
I can hit http://patrick.geek.nz/, or indeed any of my public web
stuff from home and have it go over IPv6 with no additional
configuration or effort involved. Assuming the tunnel is working, if
it's not it falls back to IPv4 nicely (not like Mail.app, which if it
can talk to it's IPv6 default route will not fall back to IPv4 if
your mail server has AAAA records, this is in itself hate worthy).
I can also hit http://noc.sixxs.net/home/ and have it show me as
coming via IPv6. (Pleasingly even with a little Canadian flag.)
For example, I just typed in http://patrick.geek.nz/ in to my browser
and got in my web server logs:
2001:4830:1226:1:217:f2ff:fe4c:9c0b patrick.geek.nz - [20/Mar/
2007:01:02:54 -0700] "GET / HTTP/1.1" 200 2883 "-" "Mozilla/5.0
(Macintosh; U; Intel Mac OS X; en-us) AppleWebKit/419 (KHTML, like
Gecko) Safari/419.3"
Which if you feel like ping6'ing it, is indeed my laptop.
Back in... some time in the past, maybe 10.3, you had to disable
http: (Simple Loader) from Debug -> Supported Protocols, as this
doesn't do IPv6, and for some reason it had a higher priority than
CFNetwork Loader. 10.4 seems to have fixed that.
Not sure why it wouldn't be working for you to be honest.
