277583 - View Page Source used cached after cache turned off

Status: RESOLVED EXPIRED

(Core Graveyard :: View Source, defect)

Description

[Mark Richards]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217 MultiZilla/1.8.0.0a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217 MultiZilla/1.8.0.0a

Mine is a sad sad story of trusting the tools and finding that they have led to
my undoing.  

I'm developing some cgi routines on a local networked embedded linux box
(http://192.168.1.90:8087/index.cgi).  The routines are all written in C.  the
debugging was quite repetitive - make a change to some code - test it - change
code - test it.  At one point I had to look at the page source so using
Mozilla's feature seemed a good option.

However what I was seeing in source and the changes I had made in my cgi routine
did not jive.  After an hour or so of this frustration, I realized that the
problem might be cache, so I turned it off.  (Suggestion: A "development" mode
for mozilla that turns off cache and anything else that might make a session
non-current!).  I then closed and reloaded.  Still, my changes were not showing
and the view source seemed inconsistent with what I was doing in my C source.

So I finally wrote a routine that writes out a copy of what the CGI is sending
to the browser and sure enough view page source was way out of synch.  In fact,
despite turning off cache and reloading, it remained back where I had started
the session.

4 hours later.

I could not find a report of a similar incident like this.  Perhaps it's a fluke
 specific to my code?  I'm attaching the html that is being sent via CGI - note
there's some small javascript in it, and reference to a stylesheet - also attached.


Reproducible: Always

Comment 1

[Mark Richards]

Attachment: This is the captured raw HTML sent to the browser session from my CGI application.

Comment 2

[Mark Richards]

Attachment: The index.css file associated with the raw html also attached

Comment 3

[Mark Richards]

Note that this won't work without the CGI and the environment that it expects,
but the source can be examined to see if there's a reason within it as to why
the View Source was not updating.

Comment 4

[Boris Zbarsky [:bzbarsky]]

Mark, how did you turn cache off, exactly?

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.