268216 - No proxy authentication dialog if extension is first to request external URL

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Matt Dawson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2

As of the 2004-11-03 build, the initial interaction with password authenticating
proxy servers is having some problems. My last test of this used Mozilla/5.0
(Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2 (the
RC2 bulid released a few days back).  Prior to the build mentioned, the Firefox
behaved as expected.

The basic issue is that if an extension, not a start page/favourite/typed URL,
is the first item to use a URL requiring authentication, Firefox does not
display a dialog indicating this.  It just causes the URL to return an error.

Reproducible: Always
Steps to Reproduce:
1) Start new browser.  (Note: Ensure start page is blank or an intranet site, so
no proxy authentication occurs.)
2) Open Sage 1.3 RC sidebar and hit the "refresh feeds" button.  (Note: Assumes
internet feeds are already configured.)
Actual Results:  
Most or all feeds will be marked as having XML Parse Errors

Expected Results:  
Prior to the 2004-11-03 build, step 2) would trigger proxy authentication and
refresh the feeds OK.

To work around this issue:
3) Open a favouite (not RSS feed) pointing to an external web page. This
triggers authentication against the proxy server and will load the page OK
provided correct authentication details are provided.
4) Repeat step 2). All feeds will now refresh properly.

PS I also noticed that during a second test of this issue, I had to try step 3)
twice because the first didn't trigger proxy authentication. Haven't been able
to reproduce this issue though.

Comment 1

[Matt Dawson]

I've reproduced this using the latest available Aviary build (7 Nov).  About
details:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I'm wondering whether this should be rated higher (Major?), but I'm not familiar
enough with the rating system to make that call.

Comment 2

[Matt Dawson]

Retested wth the most recent build, and the issue still occurs.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041108 Firefox/1.0

Comment 3

[Bill Gianopoulos [:WG9s]]

This is probably a regression caused by the fix for bug 267367.

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.