I had no luck with factors. Incorporating HTTP cache connected parameters specifically (beyond the HTML doc) does indeed operate for me. This hack evidently breaks the back again-forward cache in Safari: Is there a cross-browser onload event when clicking the back button? Just after fifteen ti