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.
I don't agree. It's my browser. It should do what I want it to do, not what the website wants it to do.
And what I want it to do is exactly what this guy says.
A lot of so called "browser problems" are actually website problems.
And who's the genius that decided accepting malformed html was a good idea? If the first browsers gave an error (with line numbers and explanations) instead of trying to render incorrect html people would just go back and fix it.
Error at line 1, DOCTYPE expectedBrowsers are just following this basic networking principle.
I run a small forum where clicking back and forth between forms without losing what you've typed is a very important feature. It works exactly the way this author wants in all browsers because the headers are set correctly.
Similarly, I also work on a big web application where clicking the back button and getting stale information is bad. Again, the website sets the proper headers and the information is refreshed (if appropriate) or left alone (if appropriate).
This is not a browser issue. The differences are likely caused by how different browsers implement (or don't implement) the standard.