I see from bugzilla that Darin has made a patch addressing (the opposite of) this bug. http://bugzilla.mozilla.org/show_bug.cgi?id=112564
How can I now achieve my original objective without resorting to https? (I prefer to test http before I move on https) IS IT TRUE(?) that after Darin's patch I can use HTTP header: Cache-Control: no-store to avoid my http served pages showing up in my users history or file-cache, while still allowing my users to view-source, save page, print-page. - IF NOT please indicate any other header trick I might use. BTW my application is for electronic patient records and not banking. The more I can leverage the browser technology to save on server config the better!
