210065 - view frame source -> save : doesn't save what is viewed

Status: RESOLVED DUPLICATE of bug 177329

(Core :: Networking: Cache, defect)

Description

[gustavo]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313

When I used view frame source -> save  to save the source for Bug 210063,
mozilla didn't save it as it should. It saved:

http://cloudy.daemon.sh/~gustavo/mozilla-bad.html

where it should have saved

http://cloudy.daemon.sh/~gustavo/mozilla.html

Please NOTE: that the problem is that mozilla doesn't save what is in the source
viewer. Instead it tries to get the page again and somehow gets confused. For
example if you load the source to the viewer, let the banking session time out
and ask mozilla to save the source....it will save the timeout message from the
web site.

Reproducible: Always

Steps to Reproduce:
1.view frame source
2.wait for the session to expire / or don't wait at all
3.save the frame source and compare with the results in the viewer

Actual Results:  
It saved the wrong contents

Expected Results:  
It should have saved exactly as seen in the viewer.

Comment 1

[Felix Miata]

Could be another bug 40867 or bug 115174 dupe. If the latter, it needs
resummarization to make a search more likely successful.

Comment 2

[gordon]

I wonder if this is a dup of bug 177329.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Very possible, yes.

Comment 4

[andrew]

Same problem (using multiple frame sets)... 

Doesn't seem to matter if:
1) right-click (in frame) this frame -> save as, or
2) view this frame source, menu -> file -> save as

You *can* copy the viewed source to the clipboard, but on paste, you get some
format mangling (extra cr/lfs on windows).

Comment 5

[Hynek (Pichi) Vychodil]

Mozilla Firefox 0.9.3 and Mozilla 1.7.2 still have this bug. Tipically remove /
form end of tags. I can see in frame source view correct xhtml. I can't save
page as in source viewer, but only in This Frame ... Save Frame as and I get
invalid xhtml.

Comment 6

[Hynek (Pichi) Vychodil]

Attachment: correct source in viewer

See / at end of meta tag.

Comment 7

[Hynek (Pichi) Vychodil]

Attachment: screwup source saved by Save Frame as ...

Comment 8

[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 9

[Felix Miata]

I tried to reproduce comment 0 using http://nbchurch.org/ and Linux SeaMonkey
1.0a, which pegged the CPU for several minutes, then died.

Comment 10

[Robert Lange]

The reproducer site no longer seems to exist. Right now we would need a new reproducer site to give a confirmation test case. It would have to be publicly available and preferably reliable. (That is, we should know it will still be available a couple of years from now.) Unfortunately, I can't think of such a publicly available site right now.

However, a couple of weeks ago I took a university survey, and I am 99% certain I encountered this bug. I was working on page 10 of the survey, then went back using the browser's back button and viewed the HTML source of page 8. Then I did a Save-As of the page source. However, when I attempted to edit the source in my HTML editor, I noticed something was wrong; it was not the same text as what was in the View Source window. After investigating, I determined it was the source of page 10. I didn't think to investigate further at the time, but my conjecture was that the Save-As command had reposted the page, and the server CGI logic returned the latest "unfinished" page.

Comment 11

[Kevin Brosnan]

*** Bug 343843 has been marked as a duplicate of this bug. ***

Comment 12

[mozilla]

Adding myself on CC:.

Comment 13

[mozilla]

Bug 288462 provides the full summary of all related issues, complete with RFC violations.  Should be linked to this one.