270631 - "Use same proxy for all protocols" doesn't work

Status: RESOLVED EXPIRED

(Firefox :: Settings UI, defect)

Description

[andrewz]

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

When I do not fill out SSL proxy and use "use same proxy for all protocols," I
cannot visit SSL web sites.





Reproducible: Always
Steps to Reproduce:
1. I check Manual proxy configuration.  
2. I check "use same proxy for all protocols."
3. I fill out the first one (HTTP proxy).
4. I try to visit an https web site: I get connection timed out

5. I uncheck use same proxy for all protocols.
6. I fill out SSL proxy (same as HTTP).
7. I can visit SSL web sites.
Actual Results:  
As stated above, I get time out the first way and success the other way.

Expected Results:  
Honor the setting "use same proxy for all protocols."

Port 80 forwarding is disabled on our network, so we use only proxies
(Squid+Dansguardian) to access web sites.

Comment 1

[andrewz]

Additional steps

8. Erase stuff in SSL Proxy.
9. Check "use same proxy for all protocols."
10. Works.

11. Erase Firefox profile directory.
12. Doesn't work (steps 1-4).
13. Notice direct (non-proxy) connection attempts in iptables log.

Comment 2

[Mike Connor [:mconnor]]

If you look at the SSL proxy info, it should match (albeit greyed out) the HTTP
entry.  There is a bug that if you type and then hit Enter without switching
fields, the value doesn't get copied across properly, if you click OK it works
though.

Comment 3

[Thomas Graham]

This is _still_ a bug, and occurs in linux and mac versions too.

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.

Comment 6

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change