W3 Total Cache Causing 302 Found Redirect to Homepage
Installed W3 Total Cache on a new site. Turned on Cache and CDN. Seems to work great except on one of the custom post types. This action happens with any option turned on.
When I visit the custom post type, I get a 302 found response, and then it redirects to the homepage. Checking the HTML before it redirects, the output looks like this:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv="Content-Type" content="text/html; charset=windows-1252"></HEAD> <BODY></BODY></HTML>
Normally headers will look like this:
<!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>.....
With CDN turned on, the 302 found redirect still happens, but only on a first visit. If I visit the page again, it renders correctly.. I’m guessing because it was cached? This does not happen on the other custom post types, just one of them.
I’ve tried a number of things including:
– Re-saving the permalinks
– Changing the .htaccess to move the WordPress redirect up to the top.
– Uninstalling the plugin and all files and trying again.
– Trying only turning on Cache or CDN or both at the same time. All get the same result
– Turning off apache modules – cache, disk_cache, pagespeed
After spending a few hours searching and trying different things, I am all out of new ideas to try.
Thanks in advance!
- The topic ‘W3 Total Cache Causing 302 Found Redirect to Homepage’ is closed to new replies.