=== Simple Cache Killer ===
Contributors: jcummings1974
Donate link: http://www.jcummings.net
Tags: cache, caching
Requires at least: 3.0.1
Tested up to: 3.5.1
Stable tag: /trunk/
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

Granular control over the type of caching instructions sent back from your sites pages, both HTML META and HTTP Caching headers

== Description ==

This plugin was born out of the need to have some sites on our multisite network that we could force to never use any type of caching - server or client.  We didn't want to do this for our entire server, so setting this up through the webserver wasn't a practical option.  Instead, activating this plugin allows you to specify which of the types of caching instructions you'd like your sites pages to include.  Each can be turned on/off easily by clicking a checkbox next to that type of caching in the admin settings panel.

== Installation ==

This plugin was built specifically for multisite networks, but should work on any Wordpress site.  The obvious benefit though, will be when you're hosting multiple Wordpress sites from a single installation/server and need to adjust the caching instructions sent by just one site.


1. Upload `plugin-name.php` to the `/wp-content/plugins/` directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. Visit the `SCK Settings` section of your settings menu to set the types of instructions you want to use.

== Frequently Asked Questions ==

= What types of caching instructions does this plugin support? =

There are two `sections` of the settings screen, an HTML META tag section, and an HTTP Headers section.  Once activated, you can choose to include the following instructions in your request responses:

1. META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE"
2. META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"
3. Pragma: no-cache (HTTP header)
4. Cache-Conrol: no-cache, no-store, must-revalidate (HTTP header)
5. Expires: 0 (HTTP header)

= Which type should I use? =

It depends on what you're trying to do I suppose. The reason that I wrote this was because I had some sites that had content that was updated frequently, and the server side Wordpress and bytecode caching, as well as client browser caching was making it hard to predict how long it would take for some changes to become visible.  For best results, turn them all on, and you can be sure that the content being served from the site the plugin is active on will always be fresh.

== Upgrade Notice ==

== Screenshots ==

== Changelog ==

= 1.0 =
* Initial release