340700 - Some servers not accessible after update to 1.5.0.4

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Lprates]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3

I just updated Firefox yesterday. I am behind a firewall and I can browse www.mail.com, www.m-w.com, www.yahoo.com, but not https://bugzilla.mozilla.org/enter_bug.cgi neither www.gmail.com.
I have not perceived this behaviour before the update...
With IE 6.0 I have no problem to access the same pages using the same proxy configuration.
The interesting point is that I can reach the page: http://gmail.google.com/mail/help/about.html but not http://gmail.google.com
I can also reach: http://www.mozilla.org/support/firefox/ but cannot reach:
https://bugzilla.mozilla.org/ neither https://bugzilla.mozilla.org/enter_bug.cgi

Reproducible: Always

Steps to Reproduce:
1.Start Firefox
2.Type www.gmail.com
3.Press Enter

Actual Results:  
The following message appears:
The connection has timed out
The server at bugzilla.mozilla.org is taking too long to respond.
 *   The site could be temporarily unavailable or too busy. Try again in a few moments.
    *   If you are unable to load any pages, check your computer's network
          connection.
*   If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

Expected Results:  
Forefox should have oppened the page

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Just to confirm, you updated to Firefox 1.5.0.4 ?

What are you using as a proxy ? Is it local on your machine or elsewhere on your network ? If it is remote, do you run a software firewall on your local machine ?

Have you ruled out wonky extensions by starting Firefox in safe mode ?
  http://kb.mozillazine.org/Safe_mode

Comment 2

[Lprates]

Hi Thomas !

I'm sorry, the correct version is 1.5.0.3.

I am using Firefox at work, so the firewall is in the LAN. In my computer I have the Sygate Security Agent.

I tried the same pages using Firefox in safe mode, but I got the same error messages.

Thanks,

Leo

(In reply to comment #0)
> User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR
> 1.1.4322)
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.3)
> Gecko/20060426 Firefox/1.5.0.3
> I just updated Firefox yesterday. I am behind a firewall and I can browse
> www.mail.com, www.m-w.com, www.yahoo.com, but not
> https://bugzilla.mozilla.org/enter_bug.cgi neither www.gmail.com.
> I have not perceived this behaviour before the update...
> With IE 6.0 I have no problem to access the same pages using the same proxy
> configuration.
> The interesting point is that I can reach the page:
> http://gmail.google.com/mail/help/about.html but not http://gmail.google.com
> I can also reach: http://www.mozilla.org/support/firefox/ but cannot reach:
> https://bugzilla.mozilla.org/ neither
> https://bugzilla.mozilla.org/enter_bug.cgi
> Reproducible: Always
> Steps to Reproduce:
> 1.Start Firefox
> 2.Type www.gmail.com
> 3.Press Enter
> Actual Results:  
> The following message appears:
> The connection has timed out
> The server at bugzilla.mozilla.org is taking too long to respond.
>  *   The site could be temporarily unavailable or too busy. Try again in a few
> moments.
>     *   If you are unable to load any pages, check your computer's network
>           connection.
> *   If your computer or network is protected by a firewall or proxy, make sure
> that Firefox is permitted to access the Web.
> Expected Results:  
> Forefox should have oppened the page

Comment 3

[Steve England [:stevee]]

Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!

Comment 4

[Steve England [:stevee]]

No response from reporter re: comment 3 -->INCOMPLETE.
Reporter, if you still see this problem with the latest release of Firefox 2, please reopen this bug. Thanks!