Using caching headers we disallow the browser from caching the pages. It looks like Safari ignores these caching headers. Therefore it looks like a Safari bug. We need to verify this, look for an open bug with Safari and if one does not exist, create a new one.

This problem might also prevent us from implementing JRA-14031, as removing the "no-store" value from Cache-Control could break this behaviour on other browsers. Need to check.

I investigated this issue to a great extent. Unfortunately, this seems to be a bug that was introduced in Safari 3.1 for Windows (Safari 3.0.4, which I tested, works fine).

The problem is that Safari 'remembers' the form's values and JavaScript variables - seems like some sort of caching problem. I tried to create a workaround where I would 'reset' the remembered value (that is used in JIRA to prevent re-submitting the form twice) via window.onload handle. Unfortunately, I hit the wall there as well as Safari does not seem to execute the onload function when you return to the page via back button.

I think that I have spent enough time investigating this issue and given that Safari is not quite popular browser choice on Windows and the fact that is a browser bug, I decided to close this bug as "Won't Fix" hoping that one day Apple will fix Safari on Windows.

Kind regards,
Dushan

Chris Owen knows a great deal about this.