From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.17-14 i686; en-US; 0.8.1) Gecko/20010326 BuildID: 2001032614 When I "Save As..." on a page that has frames and/or was generated by a CGI script or .JPS program or the like, and then I try to reload the page that I saved, I don't see the text that was displayed in the browser when I saved, but rather something different; the behavior seems to be as if I had rerun that CGI/JPS script instead of saving. What happens with Mozilla is that something else is saved. I'm not sure exactly what, but I think it's the source of the thing that generated the page. Or maybe it's only the frame around what I wanted to save. Not sure ... Reproducible: Always Steps to Reproduce: 1. Open up a Web page whose graphics are displayed produced by a .CGI or .JSP or something. 2. Select "Save As..." and save as a .HTML file. 3. Load the file just saved into the browser. Actual Results: The output produced is not what I meant to save, but rather seems to be the output that would've been produced if I had reloaded the page generated by the CGI/JSP instead of saving ... Expected Results: When I "Save As..." (at least as an HTML file), I expect that the literal HTML of the currently-displayed page will be what is saved, and I can then display this HTML which will contain the (static) contents of what I was seeing in the browser when I saved. This is how IE and Netscape 4.x and earlier work. This is truly annoying, and doesn't seem to have a workaround. For example, when I do a transaction on-line (on-line banking, etc), this is usually driven by some sort of CGI/Javascript(s); the display confirming my transaction often displays a confirmation number and a message. I like to save these messages for future reference, and in the past I've been able to just "Save As...", enter a file with a .htm(l) extension, and when I subsequently loaded that file up in the browser, the text of the confirmation (exactly as it was on the screen when I saved -- frames and all -- except perhaps for some missing images which may not get saved -- although IE does save the images also).

see bug 11632. also see bug 40867. Which of those seems more relevant to the actual problem here?

the core issue is that we reran the cgi. *** This bug has been marked as a duplicate of 40867 ***