geekpub

Yes, gone… it works with xcache as well.

and running latest version of WP too ??

When I activate the cache (disc enhanced) and use the W3 Validator, the 1st checkup, when the page is uncached, runs fine. the second one, when a cached page is served, I get a 403 Forbidden…. not a 404, that was my error.

I’m running on a VPS, and yes, I’m using the latest version of your plugin.. (re-installed yesterday)

The blog is running in a folder named geeksaresexy.net

Here you go:

Note that I had additional security directives in the middle, but I removed them for the test.

As I said, the plugin works fine with xCache.. is there any reasons why I should be using the disc (enhanced) mode instead?

<Limit GET HEAD POST>
order allow,deny
allow from all
</LIMIT>

<files wp-config.php>
Order deny,allow
deny from all
</files>

Header unset ETag
FileETag None

** <W3TC DIRECTIVES HERE> **

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Yeah, I also tried moving them under my directives, on top of the wordpress ones. and got the same results.

Hmm, moved the directives on top of the .htaccess file, still the same results..

So I installed and enabled xcache. which seemed to have solved the problem. Xcache doesn’t add anything to the .htaccess file.

Question: does it bring the same performance benefits as the disc (enhanced) mode?

Thank alot for your time Frederick, I really appreciate what you’re doing.

Hmmm, there’s no W3TC Directives in the root .htaccess of my site… only wordpress stuff and some security tweaks.

Thanks Frederick! ??

Putting the cache in Disk basic mode made everything work… and page creation time is as quick as with enhanced mode… as soon as I put it back in enhanced, it stops working.

Are there any advantages of tweaking my htaccess to make the cache work in enhanced mode?

Also, when you say “move the W3TC .htaccess directive” to the root of my blog, you’re talking about the one in wp-content\w3tc\pgcache right?

Thanks for the awesome plugin! ??

Yan

Another update: Most user agents (Stumble upon, etc..) get a 404 when accessing any page with the page caching option on. Even the W3C validator gets served a 404! https://validator.w3.org/

After disabling it, the page is accessible again.

I tried using my old hypercache plugin with W3 (page caching off + W3 minify on + W3 CDN on), and it seems to be working fine.

Any idea why W3 cached pages could be serving 404s to user agents?

Even the W3C validator gets served a 404! https://validator.w3.org/

Some additional Details:

I compared the source of each page, after and before enabling caching (one worked on facebook, the other didnt), and the ONLY difference in the page is this.

NO CACHED (below)
———-
< Content Delivery Network via geeksaresexy.geeksaresexytech.netdna-cdn.com
<
< Served from: https://www.geeksaresexy.net @ 2010-04-13 00:55:29 –>

———————-
CACHED (below)
——
> Page Caching using disk (enhanced)
> Content Delivery Network via geeksaresexy.geeksaresexytech.netdna-cdn.com
>
> Served from: https://www.geeksaresexy.net @ 2010-04-13 00:50:06 –>

It makes absolutely no sense to me.

A few extra details:

I kept the plugin enabled (with the minify and CDN option turned on), and only disabled the page caching option, and everything started working again. As soon as I turned Page caching on again, it stopped working.