Perhaps the problem lies with what the browser does when no cache control headers are present? I just checked with by loading and then leaving a Guardian.co.uk

Perhaps the problem lies with what the browser does when no cache control headers are present? I just checked with by loading and then leaving a Guardian.co.uk page, and Safari reloads it from server when you click back. Checked both the page headers and the HTTP headers, and there's no expiry date set anywhere. My preference in this case would be for back to work "properly" unless a site explicitly requests a reload. Doing it that way would solve another back issue that stings me from time to time that the author doesn't mention: forms. I'll have filled out a form, hit submit and hit a network snag for some reason or other. Try to hit back to rescue all that typing, and the browser tries to reload the damn form. Stuck. When I hit back, all I want is to go to the previous page, instantly, precisely as I saw it when I clicked the link to take me away. No reloading, nada.