833652 - upgrade to 2.15 yields "proxy server refused connection" but no proxy configured

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[Daniel B.]

User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 SeaMonkey/2.14
Build ID: 20121118021532

Steps to reproduce:

I started with a profile that worked fine with SeaMonkey 2.14.  (In particular, 2.14 could retrieve pages fine, not reporting any proxy errors; and I haven't configured it to use any proxy.)

I installed and executed SeaMonkey 2.15.1. 
Then I tried loading some regular web pages (i.e., HTTP-retrieved pages, as opposed
to local file:/... pages).



Actual results:

SeaMonkey said it couldn't connect to the proxy.  (It presented a proxy-error page that starts with "Proxy Server Refused Connection" instead of retrieving the requested pages.)


Expected results:

SeaMonkey should have retrieved the requested pages successfully (as version 2.14 does).


NOTE:  When SeaMonkey opened the initial browser window, it did successfully load the 
pages in the tabs from my saved session.  However, if I try to reload one of those tabs/pages, 
I also get the proxy-error page.  

That suggests that earlier, when SeaMonkey is restoring the previous session, the proxy 
processing works fine (does not try to use a proxy), but somewhere between there and 
the end of initial setup, the proxy setting gets changed or misinterpreted and then the 
proxy processing thinks it is supposed to use a proxy.


Note:  SeaMonkey 2.14 displays the profile's proxy setting as being set to the "Use system 
proxy settings" option.  I don't know what SeaMonkey might be looking at on Linux
 (especially on my system without Gnome or other (full) desktop layer yet), so I can't 
check that, but, any case, SeaMonkey 2.14 works fine and 2.15 doesn't.


(Note:  That proxy-error page would be more useful if its text identified the proxy server (host and port; and URL?) and the originally requested URL.)

Comment 1

[Daniel B.]

Additional data:  

The problem occurs for "http:..." URLs but not for "https:..." URLs.

Comment 2

[Tony Mechelynck [:tonymec]]

(In reply to Daniel B. from comment #0)
[...]
> NOTE:  When SeaMonkey opened the initial browser window, it did successfully
> load the 
> pages in the tabs from my saved session.  However, if I try to reload one of
> those tabs/pages, 
> I also get the proxy-error page.  
> 
> That suggests that earlier, when SeaMonkey is restoring the previous
> session, the proxy 
> processing works fine (does not try to use a proxy), but somewhere between
> there and 
> the end of initial setup, the proxy setting gets changed or misinterpreted
> and then the 
> proxy processing thinks it is supposed to use a proxy.
[...]

Another possibility would be that your previous session pages were reloaded from cache, and that SeaMonkey only tried to access the Web when you hit Reload.

Comment 3

[Daniel B.]

(In reply to Tony Mechelynck [:tonymec] from comment #2)
> ..
> 
> Another possibility would be that your previous session pages were reloaded
> from cache, and that SeaMonkey only tried to access the Web when you hit
> Reload.

Right.

Comment 4

[Daniel B.]

Going to about:config and resetting some proxy settings that were at non-default 
values (e.g., network.proxy.http) back to their default values seems to have 
worked around the problem.


The problem seems to be that the implementation of the "Use system proxy 
settings" case (network.proxy.type=5) doesn't properly ignore other proxy 
preference values (e.g., an HTTP proxy host name left in network.proxy.http
from using "Manual proxy configuration" earlier).

For example, maybe some code uses the value of network.proxy.http to 
decide if there's an HTTP proxy without first checking the value of 
network.proxy.type.

Comment 5

[Phoenix]

That may also be fixed in 2.15.1 as there are four proxy related bugs resolved in it - https://bugzilla.mozilla.org/buglist.cgi?quicksearch=828632%2C828202%2C828234%2C829646;list_id=5442834

Comment 6

[Daniel B.]

(In reply to Phoenix from comment #5)
> That may also be fixed in 2.15.1 as there are four proxy related bugs
> resolved in it -
> https://bugzilla.mozilla.org/buglist.
> cgi?quicksearch=828632%2C828202%2C828234%2C829646;list_id=5442834

The bug description says:
> I installed and executed SeaMonkey 2.15.1. 

So how might the problem be fixed in 2.15.1?  That's the version that 
showed the problem!


Changing status back from WORKSFORME because the original bug report obviously 
wasn't even read completely, and there apparently was no probing of what 
case of "I started with a profile that worked fine with SeaMonkey 2.14" might
be involved.

Comment 7

[Daniel B.]

Additional data:  The profile that showed the proxy problem was a profile that
was imported from 1.1.14 (via 2.0.14).  

It might be the case that the preferences UI in 2.<current> will never get the
settings into a state that exhibits the problem, so any real testing for this
bug probably needs to set preferences individually (in about:config) to see if
they are being interpreted properly.

Comment 8

[Phoenix]

Is this still present in latest SeaMonkey version?

Comment 9

[Phoenix]

Resolved per whiteboard