272362 - proxy autodetect doesnt detect proxy for https

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Aleks.Ehrlich]

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

Working behind squid proxy when proxy's IP and port (3128) had been configured,
everything works fine when proxy set to "manual". Switching to proxy autodetect
http works but when trying to access something via https there is no response.

Reproducible: Always
Steps to Reproduce:
1. set up a network behind proxy and firewall.
2. configure firefox to connect via manual proxy (192.168.0.220:3128), using
"the same settings for all protocols" checked.
3. check that http and https work
4. change proxy settings to auto-detect
5. check that http works
6. observe that https doesn't

Comment 1

[Frank Wein [:mcsmurf]]

Can you look what the server returns/if it returns something if you type in
http://wpad/wpad.dat (or http://wpad.your.local.domain/wpad.dat). If it returns
something, can you attach this file here (maybe you want to XXX the proxy data
itself)?

Comment 2

[Frank Wein [:mcsmurf]]

(In reply to comment #1)
> Can you look what the server returns/if it returns something if you type in
> http://wpad/wpad.dat (or http://wpad.your.local.domain/wpad.dat). If it returns
> something, can you attach this file here (maybe you want to XXX the proxy data
> itself)?

Any chance to answer this question?

Comment 3

[Aleks.Ehrlich]

No, it doesn't return anything, shall it? I've never configured any "wpad" host
and written any wpad.dat.

Comment 4

[Frank Wein [:mcsmurf]]

(In reply to comment #3)
> No, it doesn't return anything, shall it? I've never configured any "wpad" host
> and written any wpad.dat.

Well, it would make sense if th would return anything ;-). The auto-detect proxy
feature works like that afaik: First it tries
http://wpad.your.local.domain/wpad.dat, then http://wpad.local.domain/wpad.dat
(etc., it goes up the chain). If none of these files or hosts exists, it just
uses direct connection. Might it be outgoing traffic to port 443 is blocked
(https), but port 80 (http) is allowed? If you're sure port 443 outgoing is not
blocked, please attach a HTTP log, see
http://www.mozilla.org/projects/netlib/http/http-debugging.html for a how-to.

Comment 5

[Jean-Philippe]

Hello. I get exactly the "reverse" bug. Using an automatic proxy configuration
http and https work fine. Switching to a manual proxy configuration, https does
not work anymore, http remaining OK. 

Swithing back to an automatic proxy configuration, https is back to normal.

Using w2000 and Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.7.5)
Gecko/20041108 Firefox/1.0. If I can help...

Comment 6

[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 7

[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.