Closed Bug 94725 Opened 23 years ago Closed 23 years ago

Incorrect/old page content displayed [request line forwarding]

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 38488

People

(Reporter: leo, Assigned: bbaetz)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; SunOS 5.8 sun4u)
BuildID:    0.9.3

After installation on my Windows 2000 SP2 system, mozilla 0.9.3 was running
fine.  It somehow has become confused, and typing in a new URL doesn't always
cause it to display the content from the new site.  If for instance I start
mozilla and it goes to the mozilla.org home page, I type in
"http://slashdot.org" and mozilla appears to retrieve the content from that site
but it re-displays the mozilla.org page instead.

I've cleared out the memory and disk cache, all to no avail.  I will remove
mozilla, delete (after saving) the information under "Application Data/Mozilla",
and reinstall to see if the problem goes away.  I will report back once that has
been done.

Reproducible: Always
Steps to Reproduce:
1. Start mozilla; goes to mozilla.org
2. Enter URL "http://slashdot.org" and hit Enter
3. mozilla.org content is re-displayed

Actual Results:  New content was not displayed.

Expected Results:  New content should have been displayed.
How did you open your Mozilla?  This is usually a result of bug 59078.
Are you using a proxy? If so, which proxy?
Answer to first question (how opened):

  I double-clicked on the icon installed on the desktop.

Answer to second question (proxy):

  The proxy is running on my machine, it's a ZDNet utility called
  CookieCop plus.  It runs on port 8100 (configurable) and you run
  the HTTP and SSL content through it for cookie management.

  As a test, I reverted to "direct connection to the internet" and
  it seems to then work fine.  The CookieCop utility was of course
  never tested against this version of Mozilla, but I wonder it it's
  doing anything that could be considered "strange"?

  Can you think of anything I can do here to assist in figuring out
  what's going wrong, assuming of course it's of interest to follow
  up on?

  Thanks!


*** This bug has been marked as a duplicate of 38488 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Sigh. From reading the source, cookie-cop looks broken as well, with the same
problem as junkbuster (I don't have a windows machine here to test with)

If you go to the debug pref panel, and turn the http version to 1.0, then you'll
be able to use this correctly.

IF you use IE, and turn http/1.1 on for proxy servers, then you should also see
the problem.

Do you have a contact address for this program, so that I can mail the author
with the bug report?
-> networking: http, and reopening for possible contact with the author of the
program
Status: RESOLVED → UNCONFIRMED
Component: Browser-General → Networking: HTTP
QA Contact: doronr → tever
Resolution: DUPLICATE → ---
Summary: Incorrect/old page content displayed → Incorrect/old page content displayed [request line forwarding]
...and to me (bugzilla won't let me do this in one step)
Assignee: asa → bbaetz
Status: UNCONFIRMED → NEW
Ever confirmed: true
Double sigh. Chalk this up to major user bozo factor.

The Cookie Cop program *clearly* states to disable HTTP 1.1... but
it's been some time since I had configured the browser, and I only
remembered the proxy configuration portion. Definitely my bad.

As for contact info, here's what I have:

Title: CookieCop Plus v1.2
Author: Mark Sweeney
Published by Ziff-Davis, Inc.

A quick Google search turns up a pointer to the program.

Apologies for the wild goose chase.

- Leo

Yeah, google turns up the program, but no contact address. If its in teh docs,
though, they must know about their brokenness. Surfing will be slower, too, as
persistent connections are disabled.

*** This bug has been marked as a duplicate of 38488 ***
Status: NEW → 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.