Closed Bug 250021 Opened 20 years ago Closed 20 years ago

Authentication window never appears

Categories

(Core :: Security, defect)

x86
Windows XP
defect
Not set
blocker

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jamesrome, Assigned: dveditz)

References

()

Details

Attachments

(3 files)

I am using build 2004070208 on XP Pro.
I can no longer access the internal sites at ornl.gov using https. A userID/pwd
box is supposed to appear. It works with IE. With this Mozilla, the box never
shows up, and I immediately get an "Authorization Required" message.

This used to work!
Summary: Authentican window never appears → Authentication window never appears
Attached image Screenshot of prompt
This worksforme with build 2004-07-05-09 on Windows XP.
I just tried it with today's build and it still fials for me.   What else could
be causing this? I am dead in the water without it.
I just tried it with today's build and it still fails for me.   What else could
be causing this? I am dead in the water without it.
James, what was the last build in which this worked for you?  Did you change any
proxy/http/networking prefs in Mozilla?
5/26 works on my laptop.
I was going through the security settings in preparation for a Class I am
teaching, but I don't think I changed anything vital. I do not use a proxy. Is
there a way I can debug this?
5/26 works on my laptop.
I was going through the security settings in preparation for a Class I am
teaching, but I don't think I changed anything vital. I do not use a proxy. Is
there a way I can debug this?
So can anyone tell why this does not work for me?
I see this for any site I've tried that uses HTTP basic auth starting with the
firefox trunk build from 2004-06-29-08, but not in 2004-06-28-08. I think this
regressed between June 28 and 29, but a cursory scan of bonsai didn't turn
anything up that glaringly obvious.

Glancing through attachment 152428 [details] it looked like once the 401 Authorization
Required or 401 Unauthorized response was received, nsHttpChannel tried to look
up the authorization but failed silently and didn't prompt the user.

It looks like there were some checkins to
mozilla/source/netwerk/protocol/http/src/nsHttpChannel.cpp around that time, but
which one could have caused this isn't immediately evident to me.

Interestingly:

- a profile created with firefox 2004-06-28 doesn't prompt
- a profile created with firefox 2004-06-29 does prompt
- a profile created with firefox 2004-06-28, then used with -29, and then used
back in -28 now does prompt
Unfortunately, I said that a little backwards.

- a profile used only with -28 does prompt (it works)
- a profile used only with -29 does not prompt (it's broken)
- a profile used with -28 (working) and then with -29 (originally broken) now works

So using the profile in a build that works seems to fix the profile. However,
the only file in the profiles that differs in size after one run is chrome.rdf.
Some other files are the same length with different contents, but I do not know
how to track down the difference that causes one profile to work and the other
to fail. Once the profile is opened in both builds, all the files have the same
length.
I am bumping the severity of this to critical since many many things break and
the problem has been verified. I would also think this is blocking.

I am going back to the 6/27 build and hope it fixes things.
Severity: normal → critical
Reverting to thew 6/27 build fixes this for me.
*** Bug 250256 has been marked as a duplicate of this bug. ***
The latest (7-10) builds still do not work for me on Windows. 
But so far I can revery to the 6-28 build which does work.

The build was OK on Linux.

Is anyone working on this? 
I experienced this problem untill a couple of minutes ago.

 - I removed Mozilla Firefox using the de-installation option in
ControlPanel>Software
 - I installed the latest (nightly) build

-- some more details:
- I installed Firefox Nightly build of 7/juli on a fresh windows install, and
immediately it was impossible to get a username/password prompt when entering a
http-auth secured area. 
- Deleting the directory, and unpacking the 8/juli build didn't worked out
Willenm

Are you saying that doing an uninstall and reinstall fixes the problem? Or did
it just start happening for you now?
Yes, I deinstalled the 9/juli build and installed the 10/juli build, and
everything works right now.

Hope this helps..
hmmmm.
well, I uninstalled and reinstalled and it worked. But then I installed my
themes and extensions (diggler, enigmail, download manager and the patch) and it
stopped working again.
On my Fedora Core 2 box, Anthentication window never appears using home-made
firefox with 2004071120 trunk source (+ MNG patch from bug 18574) with the
following configuration. 

--disable-ldap --disable-mailnews --enable-extensions=default,-irc
--enable-crypto --disable-composer --with-system-jpeg --with-system-zlib
--with-system-png --without-system-mng --enable-image-decoders=default,mng
--enable-mng-type=MNG_BUILD_FULL_MNG --with-pthreads --disable-tests
--disable-debug --enable-xprint --disable-gtktest --disable-freetype2
--disable-freetypetest --disable-installer '--enable-optimize=-Os -g -pipe
-march=i386 -mcpu=i686' --enable-strip --enable-strip-libs --enable-xft
--enable-reorder --enable-mathml --enable-xinerama --enable-default-toolkit=gtk2
--without-system-nspr --enable-svg --enable-svg-renderer-libart
--enable-single-profile --disable-profilesharing


2004061619 trunk seems to work fine.
Attached file debugging log
More and more people are seeing this problem. I am raising this to a blocker. It
is impossible to use the browser without authentication windows.
Please someone fix this!
Severity: critical → blocker
Flags: blocking1.8a2?
2004071407_trunk source seems to work fine.
I built and checked both seamonkey and firefox on my Linux box.
Yes, the 2004071508 build now seems to work, so I am marking this fixed.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
No bug/patch referenced.

->WORKSFORME
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WORKSFORME
Flags: blocking1.8a2?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: