Extensions using web services do not appear to handle proxy authentification

RESOLVED EXPIRED

Status

()

Firefox
General
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: Julian Calaby, Assigned: Blake Ross)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Extensions, (specifically the Gmail Notifier) do not appear to handle proxy
authentification.

I am not sure whether this is the fault of the extension author(s) or of Mozilla
in general. This bug has been submitted to the author of this extension also.
(Doron Rosenberg doronr@gmail.com)

There is no simple workaround for this bug. (it still fails when you attempt to
log in after authentificating to the proxy)

Reproducible: Always

Steps to Reproduce:
1. Download and install the gmail notifier from
http://ftp.mozilla.org/pub/mozilla.org/extensions/gmail%20notifier/gmail_notifier-0.4-fx+mz.xpi
2. Set it to automatically log in to your gmail account on startup (if you need
a gmail account, I can provide you with an invite)
3. Start Mozilla while it is set to load pages through a proxy that requires
authentification.

Actual Results:  
the notifier, whilst working correctly when directly connected to the internet,
failed to retrieve the account status.

Expected Results:  
1. On startup, when the gmail notifier attempts to contact gmail, the standard
proxy authentification dialog appears asking me for a username and password.
2. After typing in my username and password, gmail notifier downloads the
required information for my account status.

Please note that I have only tested this with PORTABLE FIREFOX.

I am currently unable to test it with any other version due to an internet
shortage. (However I will test it with other versions when I do have internet)
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.