Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

Safari is (sort of) an HTTP illiterate

Note to self: At least Safari 5.1.2 on Windows does not respect HTTP cache control headers when they explicitely state that a page should never be cached and is expired from start.

Instead Safari always uses a cached version of the page when navigated via the back button. It’s likely Chrome and other versions of Safari are also affected. This has already been mentioned by Dave Meehan.

It seems there is no way to make Safari behave via HTTP. Only solution so far is to add an unload handler—which can be completely emtpy.

I feel dirty using this.

Thank you Apple t(-_-t)

Don't be the product, buy the product!