Open Bug 183041 Opened 23 years ago Updated 3 years ago

can't view IMAP messages while browser is waiting for .htaccess authentication

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Windows 2000
defect

Tracking

(Not tracked)

People

(Reporter: jasonkroberts, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 The mail client will not display IMAP messages while the browser is waiting for a username/password on a .htaccess protected page. The "loading" bar just keeps spinning, but the mail won't display until the password is entered (or cancelled). Reproducible: Always Steps to Reproduce: 1. Open Mail and Browser in separate windows 2. Point the browser at a site which uses .htaccess for authentication (try <http://www.healthcarecoach.com/admin/> ) 3. Without entering username/password, switch to mail client and try to view an IMAP message Actual Results: The "Loading Document..." message continued to show, message does not appear until the password entry box is closed in the Browser. Expected Results: Should have displayed the message.
this looks like a similar bug I've seen floating around - is SSL involved?
no, i don't think it has anything to do with SSL. it's a normal .htaccess-protected directory without additional encryption. i had a coworker test (win 2k, moz 1.2) immediately after i filed the bug and he got the same result -- the mail client just sat there and thought until we cancelled the user/pass box in the browser.
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: huang → gchan
there are dups of this around - a modal dialog in the browser blocks mail news. It's some sort of event pumping problem, I guess - I'll try to find the original bug...
I also see this on a SSL authentication (to a colbolt box) using BuildID 2004100306 on Win XP SP2
Product: MailNews → Core
Product: Core → MailNews Core
QA Contact: grylchan → networking.imap
I thought the networking rework that Darin did a while ago fixed all this...
Assignee: bienvenu → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.