The problem presents from at least Apache 2.2 and lighttpd. I have not tested other servers.
The three files in that directory can be retrieved from http://core.federated.com/~jim/webkitbug/webkitbug.tar.gz
The HTTP caching is implemented at a level below WebKit, so this bug will need to be migrated to Radar if it is confirmed. I cannot reproduce the behaviour that you describe.
This is a *webkit* issue. Hitting the refresh button doesn't refresh all cached resources, hitting enter in the url bar does.
So visiting the page, following the link, waiting, hitting back, and then hitting enter in the url bar does a correct refresh, whereas just using the reload button does not.
Oliver, I don't think the problem is what you think it is. The case you're thinking of affects HTTP as well as HTTPS sites. Signs point to this being outside of WebKit as I can reproduce this in 10.4 with the most recent nightly build, but not on 10.5. However, as the reporter mentions, it does not reproduce with Safari 2.0.x. That makes things a bit more confusing. I guess we need a little more investigation to see what is happening on reload that causes this to not work correctly.
I can confirm this is a regression from shipping Safari 2.0.4 (419.3) with original WebKit on Mac OS X 10.4.10 (8R218).
I checked the test cases, and webkit does not exhibit this problem if I cause the reload by pressing enter in the url bar, but it does if I press the reload button or shift-reload.
The autospade script confirms that this regression occurred in Big Back/Forward Cache Rewrite of r18541:
Works: r18540 Fails: r18541
Committed revision 25779.