Besides the General Settings SuperCache Manager also provides you with Advanced Settings. By using them you can fine tune the caching system. You can also specify cookies and server HTTP headers to be included or excluded from caching.
Once SuperCache is activated, it will cache content by default even if the web client query contains cookies. The tool will also behave differently towards certain HTTP headers in the source server response.
Types of Caching When Using Cookies 
The types of caching when using cookies depend on the cookies available in the visitors‘ queries sent to the website.
Here you can specify what actions the caching system will take depending on the cookies generated by your website.
Cache Everything
This caching option is active by default as it means that clients are always served cached contents no matter if their queries to the website have cookies or not.
Cache Everything Excluding Specific Visitor Cookies
With this type of caching cached content will be served to visitors, except for cases when they send a specific cookie (or cookies). You can specify cookies which will determine if the visitor will be served cached content upon website query.
Do not Serve Content from the Cache when a Cookie is Present
Add cookies to the option Do not Serve Content from the Cache when a Cookie is Present. You need to enter only the cookie name without its value. For example, if the cookie is “language=bg-BG”, you will enter only language in the field.
You can add more than one specific cookie by using Add a New Entry. You can also remove a specific cookie from the list by using the X on the right.
Serve from Cache Only if the Visitor is not Using Cookies
This type of caching serves cached content only if the client query to the website is not using cookies at all.
Here you can specify cookies to be excluded from this rule.
Ignored Cookies
Below the Ignored Cookies option you can set specific cookies to be ignored. This means that the visitor will be served cached content despite their usage in the website query.
You will see a few suggestions in the field for entering a cookie as you can select one of them. These are cookie’s presets used in widespread systems and services as they are ready made for you to add them as an exception per one click.
Disable the processing of server headers
The caching system complies with the response headers by default. They are specifically: Expires, Cache-Control and Set-Cookie.
Depending on the type of the response header, caching might behave as follows:
Expires – If the website returns an Expires header, specifying validity shorter than the caching time, the current resource will be cached for the time specified in the Expires header.
Cache-Control – If the website returns a Cache-Control header defining specific features or restrictions for the caching type, they will be taken into consideration.
Set-Cookie – If the website returns a Set-Cookie header, the current resource will not be cached.
Ignored Vary Headers
The HTTP Vary header is the primary mechanism for notifying intermediate caching systems that the website content varies depending on the specifications of the requesting web client. One of the most common directives in this header is: Vary: User-Agent.
SuperCache complies with the Vary header sent by the website. If you would like the caching system to ignore a certain Vary header directive, you can add it in this option.
HTTP 404 Error Pages
By using Cache Error Pages (HTTP 404) you can activate caching for the website responses with the 404 Not Found status code.
SuperCache will not cache a resource if its HTTP status code is 4xx or 5xx (signifying errors).
The option is deactivated by default. Click On to activate it.
Mobile Version
This option enables SuperCache to store two separate cache versions of the pages. If the User-Agent is coming from a mobile device, the tool will store a separate copy of the page in the cache.
Automatically Added URL Addresses Which are Not Cached
If the URLs added by default are present in the client query, cached content will not be served.
These are URLs providing access to the admin panels of some of the most common CMS. Disable this option if you want cached content to be served for the specified URLs.
