Closed Bug 481834 Opened 15 years ago Closed 14 years ago

Not displaying the right source code if there are 2 different pages in cache with the same url.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 136633

People

(Reporter: lacteus, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7

If I open the same dynamic page (same url) but with a different content, the source code is always displaying the source from the last loaded page, even in the previous loaded page.

So the source code is not matching what I see in the previous tab.

It's particulary disappointing when coding a website. I know there are plugins like Firebug, but sometimes I want to see the exact source code I'm getting from the server. And I want to work with tabs :)

Reproducible: Always

Steps to Reproduce:
1. Open a dynamic page (like php, asp or jsp) in a tab (url: http://mysite/page.php)
2. Open the same dynamic page in a second tab, but with a different content (same url: http://mysite/page.php)
3. (OPTIONNAL) Close the (tab) last loaded page.
4. Show the source code from step 1 on the first tab : the source code is the one from the last loaded page (the second tab source code).


Actual Results:  
The source code is the one from the last loaded page (the second tab source code).
More disturbing when you closed the last page.

Expected Results:  
The source code displays exactly what I see in the current tab.

Maybe there is a same problem with PDF files opened with Adobe plugin.

If I open a first PDF from an url, then generating a different PDF, but coming from the same url, the first PDF is shown again.

If I close the tabs with the url, then getting again the PDF, I get the right one, not in cache.

Using No-Cache Headers tricks is not working.

Disturbing when testing PDF generation :)
This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Why the hell do you consider this incomplete? What more do you want to know than what was already written? Did you try reproducing?
as requested on irc
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INCOMPLETE → ---
Has the original reporter responded?
well on irc he cane on and told us to open it again in #firefox

Did you try reproducing this problem
Whiteboard: [CLOSEME 2010-11-01]
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.