User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; FDM; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) Build Identifier: FF 2.0.0.6 When user is behind a proxy, thanksfully to the resolution of bug 312473, if an extension need to be updated at startup the proxy auth request will popup. Unfortunately, after the extension has been updated, when FF restart the proxy auth is requested again accessing the first page. Credential are not cached. The request is to cache proxy auth request and/or introduce a preference option to automatically send proxy auth requests without user intervention, when those informations have been validated by a previous successfully proxy auth. Reproducible: Always Steps to Reproduce: 1. Put FF behind a proxy, having an extension requiring upd 2. Start FF, confirm auth request, download extension update 3. FF will restart and reask auth upon first url loaded Actual Results: User are promted twice for auth Expected Results: User should be prompted only once A better behaviour would be to have a preference for authomatic authentication without any pre-filled username/password.

Added cc to robert as requested

note: the solutions regarding caching are beyond the scope of fixing this bug.

I can take a look over this to see if it's anything obvious. I suspect the issue is lacking a window inside of the xpinstall code that calls the authentication dialog.

Dave, wouldn't this be due to the application restarting after the first authentication?

Thanks Rob, that's a far more likely, if not defiantly the scenario. And it also probably makes it quite difficult to fix, potentially even undesirable to do so since it would require keeping things alive across the restart.

I'm going to move this back over to the EM. I'd like to remove the need for a restart (perhaps managing teardown) during startup which isn't really an EM bug though it affects the EM and other components like OS Integration. I'm going to discuss this with bsmedberg when he's here next.

Maybe related to this bug see also https://bugzilla.mozilla.org/show_bug.cgi?id=339804#c23

So this should hopefully be fixed by bug 576553.

(In reply to comment #9) > So this should hopefully be fixed by bug 576553. Dave, shouldn't this bug be fixed now?

Yes, fixed by bug 576553, not sure we have a way to test proxy auth right now though so a manual test would be required

(In reply to comment #11) > Yes, fixed by bug 576553, not sure we have a way to test proxy auth right now > though so a manual test would be required Even a manual test wouldn't be that easy. We do not have a solution yet to setup a proxy with auth. Lets see how we can make progress on it next year. Does it mean to be absolutely in-testsuite-?

Given that we've moved downloading the updates to during runtime rather than at startup the chances of us regressing this is extremely slim so it is probably not worth tracking this for testing purposes.

I think we can safely mark it as verified fixed. Without the application restart for extension updates we don't have this problem anymore.