Re: Where "always" means "come hell or high water"

[prev] [thread] [next] [lurker] [Date index for 2007/03/20]

From: Phil Pennock
Subject: Re: Where "always" means "come hell or high water"
Date: 03:31 on 20 Mar 2007
On 2007-03-15 at 23:39 -0700, Phil Pennock wrote:
> Safari's nice, but I avoided it for not having tabs; fortunately, I was
> just being blind.  Safari might be my new standard Mac browser, now that
> I've noticed that there's an option to enable use of tabbed browsing.
> Even nicer after you get a bunch of tools for things like DOM browsing
> by turning on the Debug menu.  My only remaining gripe is that by
> default http: doesn't support IPv4; they short-circuit a bunch of the
> lookup functionality which is present in https: handling.  If you turn

Clearly I meant "IPv6".  *cough*  Clearly.

What's curious is that my Kerberised web pages (WWW-Authenticate:
negotiate) which are all IPv6-based (since I only have one public IPv4
address) do all appear to work.

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).

I'd hate this confusion far more if it didn't mean that Safari is the
first browser to support Kerberised HTTP out of the box with no
tinkering of config options.  Firefox can be made to work with some
about:config tinkering, now confirmed on MacOSX as well as Windows.
Camino plain does not work.  The Mozila framework's trace logging
confirms that it's not tried.

But it's not a matter of a concerted effort by Apple to make their tools
"work" with Kerberos.  Otherwise they wouldn't have gone and built
curl(1) with --negotiate disabled.  *sigh*

Ah well, I once more can browse my subversion repository's web
interfaces with SSO.

-Phil
There's stuff above here

Generated at 14:02 on 20 Mar 2007 by mariachi 0.52