Closed Bug 146642 Opened 24 years ago Closed 3 years ago

Open in new tab renders wrong, reload renders correctly

Categories

(Core :: Layout, defect, P3)

x86
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: pascal, Unassigned)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205 BuildID: 20020205 The above URL is the starting URL for a search page that I was not able to grab directly (statefull server it seems). When I select a search result and choose 'open in new tab', the page initially displays a text page starting with <meta name='GENERATOR' content='The Internet Content Control'> HTTP/1.1 200 OK Server: Microsoft-IIS/5.0 After hitting reload it renders correctly. Reproducible: Always Steps to Reproduce: (pages are in dutch, but not hard to navigate) 1. go to http://213.159.10.120/vacaturebank/zoeken/index.cfm?fuseaction=zoek&zijpad=1 2. In the top search box, select 'Erasmus Universiteit Rotterdam' 3. At the bottom of the page, click 'Vacatures zoeken' 4. Right click on any of the search results and choose 'open in new tab' Actual Results: The page shows a text only display, including the HTTP/1.1 200 OK result headers from IIS/5.0 Expected Results: a properly formatted page. Hitting reload makes the page render correctly. I tested grabbing the URL with a normal telnet session, and the correct User-Agent string. The server seems to return the content correctly consistently.
Reporter, you are using an old build. Test with a recent build, please. If problem is fixed, you can close this bug.
Sorry about the older version, the Bug still exists in Mozilla with User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020516 I cannot test an even more recent version until Ximian updates their RPMs (Ximian-desktop on RH7.1, updated yesterday) Regards, Pascal.
WFM, 1.0 RC2 on Linux. Maybe this is a HTTP 1.1 issue? Reporter, always inform in the bug report if the build isn't from vanilla mozilla distribution. Better yet, try with a latest Mozilla release. (You can install it into a separate directory just for testing)
Alas, from a test with build ID: 2002052309 from http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.0rc3/ mozilla-i686-pc-linux-gnu-1.0rc3.tar.gz has the bug. Extracted to /tmp/mozilla/ and ran /tmp/mozilla/mozilla with no arguments, it correctly picked up my settings from my homedir. Some more tests. It seems the originating page is also important, if I create a simple page with only URL http://213.159.10.120/EUR/vacatures/detail.cfm?vacature_id=QNWTGFWW does not trigger the bug. It only works when the page comes from the same server. That makes me think of keep-alive. Yes, Keep-Alive seems to be involved in the problem, lsof shows an open connection: mozilla-b 4016 pascal 39u IPv4 284204 TCP 6-144.fol.nl:32862-> 213.159.10.120:http (ESTABLISHED) When I turn off Preferences::Advanced::HTTP networking::Enable persistent connections the page shows correctly on the first try. Changing from http 1.1 to 1.0 but leaving persisten connections has the bug. -Pascal.
Summary: Open in new tab renders wrong, reload rencers correctly → Open in new tab renders wrong, reload renders correctly
Changing QA contact to Amar
QA Contact: petersen → amar
Chnaging back to petersen for QA contact
QA Contact: amar → petersen
Confirming in the May 23rd build (2002-05-23-05 1.0.0)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Changing QA Contact
QA Contact: petersen → moied
Target Milestone: --- → Future
WFM in 6/11 and 12/26 Linux Trunk.
Pascal, can you still reproduce using a current Trunk build?
WFM, trunk build 2004012709, Win XP
Assignee: attinasi → nobody
QA Contact: moied → layout
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.