Title: WP-Super-Cache: Served supercache file from PHP Last modified: August 21, 2016 --- # WP-Super-Cache: Served supercache file from PHP * [Tom Goering](https://wordpress.org/support/users/navycs/) * (@navycs) * [13 years ago](https://wordpress.org/support/topic/wp-super-cache-served-supercache-file-from-php/) * I am using the latest version of WP Super Cache — I have been for a long time— thank you! But I just noticed I may have a problem. I followed Hostgator’s set- up found here –> [http://support.hostgator.com/articles/specialized-help/technical/wordpress/wp-super-cache-plugin](http://support.hostgator.com/articles/specialized-help/technical/wordpress/wp-super-cache-plugin) * Yet, my server header still returns “WP-Super-Cache: Served supercache file from PHP” Should I not expect a different result because I have mod rewrite selected? * My pages return at the bottom of the page something like: ` * ` * [http://wordpress.org/plugins/wp-super-cache/](http://wordpress.org/plugins/wp-super-cache/) Viewing 4 replies - 1 through 4 (of 4 total) * Thread Starter [Tom Goering](https://wordpress.org/support/users/navycs/) * (@navycs) * [13 years ago](https://wordpress.org/support/topic/wp-super-cache-served-supercache-file-from-php/#post-3996841) * The following is a reply I received from my Web host as to why issues are occurring with WP Super Cache. * I hope this helps: * > Hello there! > Sorry for the delay in response. Support queues are higher than we’d like right > now, but let’s cut to the chase: > WP Super Cache is active, configured to HostGator’s specifications, and working. > For some unknown reason, despite extensive investigation, WP Super Cache’s > own testing system fails because it is unable to resolve its own domain. The > plugin is not making a DNS request to identify where `www.navycs.com` goes. > I’ve never seen this error before, and it would be too time-consuming to go > into the plugin and pinpoint the code that seems to be problematic. If this > is concerning to you, I would recommend that you contact the developer of the > plugin with the information I mentioned in this email. > The probable explanation for why you received the “Served super cache file > from PHP” header is that the page that you read the headers from was already > cached. Flushing your browser cache and the WP Super Cache cache would force > your site to resend the page, which should not have that header value anymore. > I hope this information has been helpful to you. Please don’t hesitate to follow > up if you have any more questions or concerns. > Sincerely, > Nick L. > Linux Systems Administrator HostGator.com, LLC * Thread Starter [Tom Goering](https://wordpress.org/support/users/navycs/) * (@navycs) * [13 years ago](https://wordpress.org/support/topic/wp-super-cache-served-supercache-file-from-php/#post-3996850) * My result of the Cache Tester: * > Couldn’t resolve host ‘www.navycs.com’ > Cache Tester > Test your cached website by clicking the test button below. > Fetching [http://www.navycs.com/blogs/](http://www.navycs.com/blogs/) > to prime cache: OK Fetching first copy of [http://www.navycs.com/blogs/](http://www.navycs.com/blogs/): > FAILED Fetching second copy of [http://www.navycs.com/blogs/](http://www.navycs.com/blogs/): > FAILED > One or more page requests failed: > The pages do not match! Timestamps differ or were not found! * My server header for a page in my blog: * > HTTP/1.1 200 OK > Date: Tue, 06 Aug 2013 20:24:29 GMT Server: Apache X-Powered- > By: PHP/5.3.27 Vary: Accept-Encoding,Cookie,User-Agent Cache-Control: max-age > =3, must-revalidate WP-Super-Cache: Served supercache file from PHP Content- > Encoding: gzip Content-Length: 5740 Keep-Alive: timeout=5, max=75 Connection: > Keep-Alive Content-Type: text/html; charset=UTF-8 * Thread Starter [Tom Goering](https://wordpress.org/support/users/navycs/) * (@navycs) * [13 years ago](https://wordpress.org/support/topic/wp-super-cache-served-supercache-file-from-php/#post-3996883) * I apologize for posting again, but while looking at both sites, [http://inphotos.org/](http://inphotos.org/) and [http://ocaoimh.ie](http://ocaoimh.ie) — the sites Donncha contributes to according to the links in the admin portion of the plug-in — both return “WP- Super-Cache: Served supercache file from PHP” in the server header. I assume mod_rewrite is used as recommended on both of those blogs, but they both appear not to be serving pages as designed (according to the header). Are those sites returning the errors listed above as my site does? Am I missing something? Is there a bug, or am I the only one experiencing this issue? I would love to figure out how to get the mod_rewrite to work — Hostgator is at a loss, too. * Thread Starter [Tom Goering](https://wordpress.org/support/users/navycs/) * (@navycs) * [13 years ago](https://wordpress.org/support/topic/wp-super-cache-served-supercache-file-from-php/#post-3996920) * Does anyone have mod_rewrite option of this plug-in working?? Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘WP-Super-Cache: Served supercache file from PHP’ is closed to new replies. * ![](https://ps.w.org/wp-super-cache/assets/icon-256x256.png?rev=3506220) * [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-super-cache/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-super-cache/) * [Active Topics](https://wordpress.org/support/plugin/wp-super-cache/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-super-cache/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-super-cache/reviews/) * 4 replies * 1 participant * Last reply from: [Tom Goering](https://wordpress.org/support/users/navycs/) * Last activity: [13 years ago](https://wordpress.org/support/topic/wp-super-cache-served-supercache-file-from-php/#post-3996920) * Status: not resolved