Darin--
Awesome! This sounds like exactly what I want.
So dare I ask when this is likely to be done? :)
Mike Fleming
Darin Fisher wrote:
>
> Mike Fleming wrote:
>
> > Hi--
> >
> > I have an application that embeds Mozilla (Nautilus, specifically) and
> > I'd like to be able to store and manage HTTP Proxy authentication and
> > general HTTP authentication credentials in my embedding application.
> >
> > Specifically:
> >
> > 1) I want to be able to set HTTP proxy authentication from a single
> > location
> > 2) I want to be able to prompt a user only once for a password when they
> > visit an HTTP site that requires authentication. Currently, the user
> > will get prompted twice (once by my application, which needs to make an
> > HTTP request, and once by Mozilla).
> >
> > I understand that there's a plan in the works to be able to override
> > certain dialogs that Mozilla pops up. Although I may be able to get
> > what I want with dialog overriding, it seems like this may be
> > insufficient. In particular, I will need to be able to distinguish
> > between proxy authentication and regular authentication (the dialogs
> > currently are confusingly similar currently). I'll also want to access
> > other data present on the Authentication header (such as 'realm').
> >
> > Anyway, is there a way for an embedded application to do this thing
> > currently? (Even a relatively evil way?) Is there a plan in the works
> > to make this possible?
> >
> > Mike
>
> There is no way to do this right now. The plan (within necko) is to
> make authentication a callback on the HTTP event sink that would by
> default map to a modal dialog being thrown. Embedders with access to
> the HTTP channel could override the event sink implementation and handle
> the authentication callback as they please. This callback will include
> the realm as well as other related info as parameters.
>
> Is this sufficient?
>
> Darin
