I tried debugging this keychain stuff a while ago. Basically we're using a deprecated API for the sake of Mac OS X 10.1.5 support and its hard to figure out what is going on. I couldn't actually find any problems with the way we were handling the keychain stuff. I suspect that those older APIs just don't support some of the keychain stuff internally that we take for granted now. One of the first things I am going to do for 0.9 is move us to the new keychain API, and the idea is to solve some bugs in the process of doing that :)
-Josh On Wednesday, June 16, 2004, at 02:21PM, Bruce Davidson <[EMAIL PROTECTED]> wrote: >Charles, > >> I've noticed that Camino gets confused when a single host has more >> than one HTTP authentication realm. It appears that Camino is storing >> only the hostname in the keychain entry, rather than the host and >> realm. Would it be difficult to incorporate this into Camino's >> interaction with the keychain? > >I think thats bug 198162 >(http://bugzilla.mozilla.org/show_bug.cgi?id=198162) on Camino. I'm not >sure whether the fault lies with our use of the keychain or the >underlying necko support for basic auth. That is known to be pretty >poor, see bug 137852 >(http://bugzilla.mozilla.org/show_bug.cgi?id=137852). > >Cheers, > >-Bruce > >-- >Bruce Davidson > >_______________________________________________ >Camino mailing list >[EMAIL PROTECTED] >http://mozdev.org/mailman/listinfo/camino > > _______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
