WordPress.org

1. niska
   Member
   Posted 1 year ago #

   I upgraded to the development version. I know that this version might have bugs, but in this case there might be something wrong with my .htaccess file?

   I copied and paste the code that was suggested in the plugin into my .htaccess file. But when I access my site I get redirected to the .gzip file of my page.

   Is there something wrong with the .htaccess code?

   # BEGIN W3TC Page Cache core
   <IfModule mod_rewrite.c>
       RewriteEngine On
       RewriteBase /
       RewriteCond %{HTTPS} =on
       RewriteRule .* - [E=W3TC_SSL:_ssl]
       RewriteCond %{SERVER_PORT} =443
       RewriteRule .* - [E=W3TC_SSL:_ssl]
       RewriteCond %{HTTP:Accept-Encoding} gzip
       RewriteRule .* - [E=W3TC_ENC:.gzip]
       RewriteCond %{REQUEST_METHOD} !=POST
       RewriteCond %{QUERY_STRING} =""
       RewriteCond %{REQUEST_URI} \/$
       RewriteCond %{REQUEST_URI} !(\/wp-admin\/|\/xmlrpc.php|\/wp-(app|cron|login|register|mail)\.php|\/feed\/|wp-.*\.php|index\.php) [NC,OR]
       RewriteCond %{REQUEST_URI} (wp-comments-popup\.php|wp-links-opml\.php|wp-locations\.php) [NC]
       RewriteCond %{HTTP_COOKIE} !(comment_author|wp-postpass|wordpress_\[a-f0-9\]\+|wordpress_logged_in) [NC]
       RewriteCond "%{DOCUMENT_ROOT}/wp-content/w3tc/pgcache/$1/_index%{ENV:W3TC_UA}%{ENV:W3TC_REF}%{ENV:W3TC_SSL}.html%{ENV:W3TC_ENC}" -f
       RewriteRule (.*) "/wp-content/w3tc/pgcache/$1/_index%{ENV:W3TC_UA}%{ENV:W3TC_REF}%{ENV:W3TC_SSL}.html%{ENV:W3TC_ENC}" [L]
   </IfModule>
   # END W3TC Page Cache core

2. niska
   Member
   Posted 1 year ago #

   Could there be some other bug, that causes the user to be redirected to the .gz file?

   It only seems to happen occationaly - not all the time.

3. niska
   Member
   Posted 1 year ago #

   This is an example. When I go to the front page, http://www.mydomain.com/ I get redirected to

   http://www.mydomain.com/wp-content/w3tc/pgcache/_index.html.gzip

4. niska
   Member
   Posted 1 year ago #

   I found the error. My misstake not using the latest .htaccess code. Sorry.

Topic Closed

This topic has been closed to new replies.