Closed Bug 123689 Opened 23 years ago Closed 23 years ago

Doesn't actually load a new url when i type it in

Categories

(Core :: Networking, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 38488

People

(Reporter: nramkumar, Assigned: neeti)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205
BuildID:    0.9.8

Just compiled 0.9.8 and it seems to have a problem when running with a
junkbuster proxy.  I am trying to run mozilla with a http proxy configured
(junkbuster running on localhost, port 8000).  If I try to load
http://www.google.com, and then try to load http://www.yahoo.com, it just
refreshes google.com and never gets yahoo.com.  In fact, trying to go to any
other page from google.com doesn't seem to work.  The only exception I found to
this was I could go to mozilla.org from google.com, but again, from mozilla.org
I cannot go anywhere else except google.com.

This behavior happens only when I use the proxy.  If I don't then I don't see
this happen.  I am pretty sure the problem is not with the junkbuster proxy as
it works fine with netscape 4.7x and even the earlier mozilla M18 milestone.

Reproducible: Always
Steps to Reproduce:
1.Set up a junkbuster proxy in the localhost.  configure it as the http proxy
(127.0.0.1 port 8000)
2.Open http://www.google.com
3.Try opening http://www.yahoo.com by typing the url into the location box and
hitting enter.

Actual Results:  The tab refreshes google.com and doesn't go to http://www.yahoo.com

Expected Results:  Should've gone to yahoo.com, right?

*** This bug has been marked as a duplicate of 29856 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
wrong bug
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Please read the Release Notes about proxies.

*** This bug has been marked as a duplicate of 38488 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.