Falcon not serving cache files; cause no hidden debugging data to html

Are you logged in at the time that you are checking the site? Wordfence won’t cache pages while you’re logged in (to prevent caching possible sensitive information), or for the rest of your session after you log out of the site.

If you have a second browser on your computer, try using that one to see the speed increase and the debugging comment. I do see it on your site’s main page, currently.

If you only have one browser installed, you can log out and close all browser windows, and then then start your browser again and visit the site without logging in.

I have the same issue. The .htaccess has been modified, but the debugging data is not appearing on pages even though it’s selected. I’m not logged-in when checking, and I’ve checked with multiple browsers.

Make sure your computer hasn’t stored the wordpress cookie. I believe I used a proxy to see it on mine.

tim

I checked it using Chrome’s “incognito” mode, thinking that would be a browser with no cookies, correct? Site is here.

If I use Basic Caching, it works, but Falcon Engine doesn’t. Are you setup for situations where WordPress is not installed in the root? In that case there are two htaccess files, one in the root and one in the WordPress folder. I noticed that W3TC modifies the htaccess in the root folder, while yours modifies the one in the WordPress folder. Could that be the problem?

Mike,

Yes, that might be related. Is your installation the type where the whole site is run by WordPress, but the core files are just in another directory? Or is it the type where the main site is something other than WordPress, and WordPress only handles what is in the subdirectory (like yoursite.com/blog/)?

The whole site is WordPress, but the WP core files are not in the root. Also, revising my earlier statement, Basic Caching is also not working reliably. Sometimes I’ll see the debugging comment, other times I won’t.

Mike,

Thanks for the details — I’ll be testing this soon, and will post back here when finished.

-Matt

Mike,

We did reproduce the problem on a couple test servers with a similar setup, with WordPress core files in a subdirectory, so the dev team will be working on this. The Falcon caching issue should be fixed in a future version of Wordfence.

Basic caching does seem to be working for us, so since you do see the debugging comment sometimes, it might be that something is triggering your cache to clear. Possible reasons are included here:
https://docs.wordfence.com/en/Falcon_Cache#Events_that_cause_the_Falcon_Cache_to_auto-clear

Another reason could be that you were recently logged into the site — if you visit the site after logging out, but before closing your browser, you won’t see cached pages. This prevents aggressive browser caches from showing you pages that you saw while logged in, even after logging out.

-Matt

Hello,

I also having the issue where the debug notice is not being added to the source. I am testing using a separate browser (after all cookies and browser cache is cleared).

My .htaccess is as follows:

#WFCACHECODE - Do not remove this line. Disable Web Caching in Wordfence to remove this data.
<IfModule mod_deflate.c>
	AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json
	<IfModule mod_headers.c>
		Header append Vary User-Agent env=!dont-vary
	</IfModule>
	<IfModule mod_mime.c>
		AddOutputFilter DEFLATE js css htm html xml
	</IfModule>
</IfModule>
<IfModule mod_mime.c>
	AddType text/html .html_gzip
	AddEncoding gzip .html_gzip
	AddType text/xml .xml_gzip
	AddEncoding gzip .xml_gzip
</IfModule>
<IfModule mod_setenvif.c>
	SetEnvIfNoCase Request_URI \.html_gzip$ no-gzip
	SetEnvIfNoCase Request_URI \.xml_gzip$ no-gzip
</IfModule>
<IfModule mod_headers.c>
	Header set Vary "Accept-Encoding, Cookie"
</IfModule>
<IfModule mod_rewrite.c>
	#Prevents garbled chars in cached files if there is no default charset.
	AddDefaultCharset utf-8

	#Cache rules:
	RewriteEngine On
	RewriteBase /
	RewriteCond %{HTTPS} on
	RewriteRule .* - [E=WRDFNC_HTTPS:_https]
	RewriteCond %{HTTP:Accept-Encoding} gzip
	RewriteRule .* - [E=WRDFNC_ENC:_gzip]
	RewriteCond %{REQUEST_METHOD} !=POST

	RewriteCond %{QUERY_STRING} ^(?:\d+=\d+)?$
	RewriteCond %{REQUEST_URI} (?:\/|\.html)$ [NC]

	RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|wf_logout|wordpress_logged_in|wptouch_switch_toggle|wpmp_switcher) [NC]

	RewriteCond %{REQUEST_URI} \/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)(.*)$
	RewriteCond "%{DOCUMENT_ROOT}/wp-content/wfcache/%{HTTP_HOST}_%1/%2~%3~%4~%5~%6_wfcache%{ENV:WRDFNC_HTTPS}.html%{ENV:WRDFNC_ENC}" -f
	RewriteRule \/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)(.*)$ "/wp-content/wfcache/%{HTTP_HOST}_$1/$2~$3~$4~$5~$6_wfcache%{ENV:WRDFNC_HTTPS}.html%{ENV:WRDFNC_ENC}" [L]
</IfModule>
#Do not remove this line. Disable Web caching in Wordfence to remove this data - WFCACHECODE

Error log is shows:
[17-Feb-2016 06:32:36 UTC] PHP Warning: chmod(): File name too long in /opt/www/wp-content/plugins/wordfence/lib/wfCache.php on line 165

Question: Is wp-content/advanced-cache.php required? It exists but it is 0 bytes.

I have WP 4.4.2 installed with WordFence 6.0.24.
Wordpress is installed in a sub-directory on the domain.

When Falcon caching is turned on, I do not see the debug comment.

When regular caching is turned on, I do see the debug comment.

Was the issue with subdirectory installation of WordPress and Falcon caching resolved?

@cfc: I haven’t seen the “file name too long” error before. This might be an issue if you have very long permalinks, though I’m not sure what the limit is — you could confirm if you can see very long filenames in subfolders of the wp-content/wfcache/ directory. The advanced-cache.php file isn’t used for Wordfence’s cache, so that might be left over from a previous cache plugin that you used.

@wbgwpdev: The issue with using Falcon on sites with WordPress installed in a subdirectory has not been resolved yet. It is in our queue, but I don’t have a date for when it will be fixed yet.

If you still have trouble and need more details, can you both make a new post using the form at the bottom of the Wordfence forum here. (The www.ads-software.com forum rules ask us to keep each person’s issues separate, and it also helps us keep track of open issues, so no one gets skipped in long posts.) You can include a link to this post for reference. Thanks!

-Matt R

Hi @wfmattr,

I did find a few files with long URLs. Example:

/wp-content/wfcache/www.domain.com_60-second-skills/how-and-when-to-use-a-one-way-data-table-in-excel-vs-a-two-way-excel-data-table~~~~_wfcache_https.html_gzip

Thanks, I don’t think that filename should be too long for PHP to use chmod(), so I’m not sure what else might be causing that warning unless the host has the files in a very deep directory structure.

Since this seems to be a different issue than the original post, you can make a new post using the form at the bottom of the Wordfence forum here, and we can continue troubleshooting. Thanks!

-Matt R