Those jobs are stored in database and contain parameters with information about actions it should perform.
It's strongly recommended to run those pending jobs before upgrading the wiki, to avoid them failing in case the parameter specification of those jobs change on the new version.
It does not describe a method by which one can clear the 'traditional' browser cache via client- or server-side code, which is nigh impossible to do.
There's no way a browser will let you clear its cache.
clear Cache() should suffice if you need to clear the cache only and don't care about DNS cache and connections). And however you include your files you can set that number via a timestamp when the js-file has last been modified.
So cache will work normally if the number does not change.
Using SSL also makes some browsers The browser interprets the whole string as the file path even though what comes after the "? So wat happens now is that next time when you update your file just change the number in the script tag on your website (Example As you can tell from above commands, it not only clears the browser cache, but also clears the DNS cache and closes network connections.
NOTE: This solution relies on the Application Cache that is implemented as part of the HTML 5 spec.
It also requires server configuration to set up the App Cache manifest.
I am looking for a way to programmatically empty the browser cache.
I am doing this because the application caches confidential data and I'd like to remove those when you press "log out".
It would be a huge security issue if that were possible.