74965 - Proxy: clearing the address of the SSL proxy breaks HTTPS

Status: RESOLVED WORKSFORME

(Core :: Networking, defect, P4)

Description

[Steve Hill]

If you clear the address in the SSL proxy configuration (i.e. to make HTTPS go
directly instead of via the proxy), and then visit a https site Mozilla sits
there trying to resolve the hostname (and eventually fails).  If I run a
tcpdump, I can see the DNS requests and DNS replies.

Comment 1

[Keyser Sose]

Reporter what build id are you using?

Comment 2

[Steve Hill]

Oops, sorry - Build 2001040421

Comment 3

[[e-mail]]

Is this a problem with any direct HTTPS transaction (like w/ a new profile) or
an event-ordered problems (new profile - works fine, turn on SSL proxy - works
fine, turn off SSL proxy - breaks...)?

Comment 4

[Steve Hill]

I haven't found any particular event ordering is needed - I just clear the SSL
Proxy textbox and it breaks.  Clicking the "Direct connection" radio button
makes it work, but that turns off all the other proxies too, of course.

Comment 5

[benc]

mass move, v2.
qa to me.

Comment 6

[Keyser Sose]

Marking NEW.

Comment 7

[neeti]

gagan: pls. explain the problem with more details. benc can we have this 
reproduced?

Comment 8

[benc]

I think I know what the problem is, but I cannot reporduce the problem in this case:

When you change proxy preferences in various situations, the existing window
does not always seem willing to re-connect. It sort of goes deaf to the network,
but a new window works fine.

Either that, or it is an obscure prefs.js problem.

So here's my advice:

1- Try opening a new window when this problem occurs and tell me if it still
doesn't surf.

2- If you have a profile that is not surfing HTTPS, clip the
"networking.proxy.*" lines out of prefs.js and send it to us.

Comment 9

[neeti]

Reporter: Is this still a problem?

Comment 10

[Steve Hill]

Verified fixed (2002060904)

Comment 11

[benc]

REOPEN for RESOLVED/WFM.

Comment 12

[benc]

If there is no specific bug w/ code or patch in this bug, please use
RESOLVED/WFM in the future.

In this case, if you could now VERIFY this bug, that would be great...