Closed Bug 24329 Opened 26 years ago Closed 25 years ago

Proxy: session-length auth cache

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: gagan, Assigned: gagan)

References

Details

(Keywords: regression, Whiteboard: [PDT+] ETA 03/06/00)

Status: NEW → ASSIGNED
Depends on: 22405
Summary: Make proxy auths persistent. → Make proxy auths persistent.
Target Milestone: M13
Target Milestone: M13 → M14
Just tried Win32 build from this morning (20jan2000 9:17) under NT4, and get into a infinite loop with the database key prompt. However, it does appear to successfully authenticate.
I can also verify that the authenticated http proxy works, but I also get into an endless loop of database key prompts and re-auhentication to the proxy. I eventually got slashdot.org fully displayed after about twenty re- authentications. Same story trying to go to mozillazine.org , sometimes it would remember the username and password, sometimes I would need to re-key them. Using latest M13 build on Win95
Severity: normal → major
Keywords: beta1
PDT+
Whiteboard: [PDT+]
*** Bug 25302 has been marked as a duplicate of this bug. ***
*** Bug 25486 has been marked as a duplicate of this bug. ***
*** Bug 25861 has been marked as a duplicate of this bug. ***
*** Bug 26498 has been marked as a duplicate of this bug. ***
*** Bug 26555 has been marked as a duplicate of this bug. ***
*** Bug 26660 has been marked as a duplicate of this bug. ***
Whiteboard: [PDT+] → [PDT+] eta: 2/9/00
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Can not verify this on Linux until bug 27784 is cleared
Although I can connect and authenticate to port 80 on our firewall, this mornings build (2000021608) no longer resolves DNS entries beyond the firewall. Needless to say NS4.61 is happy as a clam.
I should have added that this was using the Win32 build under NT.
it seem in todays nightly built it's broken again (is there no way to change the resolution to broken this version of bugzilla)
tever you can verify this without the auth dialogs by setting up a proxy that doesn't do auth. We need to verify soon if we regressed!
Bug reproduced on nightly build 2000022608, MacOS 8.6 ... reopening. Ouch.
Status: RESOLVED → REOPENED
Keywords: regression
OS: Linux → All
Hardware: PC → All
Resolution: FIXED → ---
Build 2000022708 for Win32 under NT is successfully authenticating again. However, the recurring database prompts have also returned.
Gagan, the initial bug summary 'make proxy auths persistent' was working on NT and MacOS 8.6 (and probably Linux but I was waiting on 27784 before verifying). Now we seem to have regressed and the name/password dialog is popping up on both NT and the Mac again. I can access URLs through the proxy between password prompts so proxies appear to be working ... just not the persistence part. Also, I have no problems with non-authenticated proxies but I don't see what that has to do with this bug.
the reason why we are seeing these dialog boxes again is becuz the auth is failing and the auth is failing becuz of bug 27784. So marking this as blocked on it.
Depends on: 27784
*** Bug 29204 has been marked as a duplicate of this bug. ***
eta: 2/9/00 -- over
Whiteboard: [PDT+] eta: 2/9/00 → [PDT+]
marking as dup of 27784 to close this. *** This bug has been marked as a duplicate of 27784 ***
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → DUPLICATE
ok, I beleive this is working but the other bugs are in the way. Closing it out.
Status: RESOLVED → VERIFIED
This is not a dup of 27784. This bug has to do with repeated requests for http authentication on all platforms. Bug 27784 is a linux-only bug having to do with not being able to enter anything into the password field. Reopening and removing the dup indication.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
No longer depends on: 27784
*** Bug 30223 has been marked as a duplicate of this bug. ***
*** Bug 29999 has been marked as a duplicate of this bug. ***
Gagan, Assuming you agree with Morse's comment, can you give info about how significant this bug is, and how likely it is we'll see a fix RSN? Thanks, Jim
If it helps you assess how significant this bug is ... It's my catfood bug. I have around 40 Mozilla bugs on my bug scratch-pad, waiting for me to file them. But I'm waiting for this bug to be fixed first before I file them, otherwise it's far too tedious for me to work out the `steps to reproduce' for the bug reports. Besides which, the cost of downloading a browser which I couldn't use for browsing wouldn't be worth it. (By the way, tsk tsk to tever@netscape.com, for verifying an unverifiable bug ...)
Summary: Make proxy auths persistent. → Make proxy auths persistent
updating eta.
Whiteboard: [PDT+] → [PDT+] ETA 03/06/00
fixed, awaiting review/approval.
*** Bug 30821 has been marked as a duplicate of this bug. ***
fix checked in.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
*** Bug 31027 has been marked as a duplicate of this bug. ***
verified: NT 2000030809 Mac 2000030808 Mozilla build Linux 2000030809
Status: RESOLVED → VERIFIED
I can verify that this is fixed as of build 2000030908 in Win98. I now have a new default browser. THANKS!!!!! -me
Woo hoo! Works in build 2000031008 under Win95a and WinNT (even when I'm using WebWasher).
*** Bug 32264 has been marked as a duplicate of this bug. ***
*** Bug 33374 has been marked as a duplicate of this bug. ***
*** Bug 33627 has been marked as a duplicate of this bug. ***
If the "My Sidebar" is open when the browser comes up, you are forced to authenticate twice. Once for the sidebar, and once for the default home page. If the sidebar is closed, you only have to authenticate once for the default home page, at which point, when you open the sidebar, it is persistant and works. So in other words, if you authenticate with "My Sidebar" you shouldn't have to authenticate again for the default home page. Version is 2000032808 on Win98. -me
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Please do not reopen bugs becuz they are having problems in specific cases. File new ones for those cases. Filed a separate bug... bug 33825. Marking as fixed.
*** Bug 34596 has been marked as a duplicate of this bug. ***
*** Bug 34800 has been marked as a duplicate of this bug. ***
*** Bug 34700 has been marked as a duplicate of this bug. ***
*** Bug 35159 has been marked as a duplicate of this bug. ***
*** Bug 36498 has been marked as a duplicate of this bug. ***
Marking this verified once again. For the specific case of authentication with sidebar open see bug 33825.
Status: RESOLVED → VERIFIED
Nightly linux-i686-pc-gnu of 2000070308 I get this each time I go back or press a link. The proxy authorisation dialog opens and asks for the username and password. The username and password are already correctly entered though. The behaviour is not affected by whether or not the "use password manager to remember these values" has been selected
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Making the proxy auths persistent and using password manager to remember the auths are two different things. It is the networking module that makes them persistent and, if they are persistent, will not bother prompting for them each time a page requires them. Password manager, on the other hand, comes into play when networking decided to do the prompt -- in that case password manager will prefill the prompt with values that were previously saved. But you will still get the prompt that you have to dismiss. In case I wasn't clear, let me say it another way. If you don't get a prompt, then networking has made them persistent. If you get a prompt and it has values prefilled, then password manager has made them persistent.
Fix checked in.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → FIXED
verified: WinNT 2000070708 Linux 2000070710
Status: RESOLVED → VERIFIED
*** Bug 22482 has been marked as a duplicate of this bug. ***
*** Bug 112179 has been marked as a duplicate of this bug. ***
*** Bug 139737 has been marked as a duplicate of this bug. ***
*** Bug 139101 has been marked as a duplicate of this bug. ***
Summary: Make proxy auths persistent → Proxy: auths persistent
I see what is going on... This bug is originally about having auth cached so you didn't have to retype the proxy username and password for every 407 that came back from the same server. This basically works, so this bug stays verified. There have been reports of the occassional regression of this feature, if so, they belong in a new bug, and should be tracked w/ the regression keyword. Some drift has occurred in the dupes, which is a demand for proxy auth across application sessions. Password manager does not do what people want, they want transparent authentication, the way mailnews works. I've filed bug 165424 as an RFE for what people want.
Summary: Proxy: auths persistent → Proxy: session-length auth cache
You need to log in before you can comment on or make changes to this bug.